Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
maestro-core
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Analyze
Contributor analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
maestro
maestro-core
Commits
0b9b10a3
Commit
0b9b10a3
authored
Mar 12, 2021
by
Utz-Uwe Haus
Browse files
Options
Downloads
Patches
Plain Diff
Add comment about gdb usage in docker
CAP_PTRACE is needed for ASLR disable to work, which gdb needs
parent
95962b73
Branches
Branches containing commit
Tags
v2.0.0
Tags containing commit
1 merge request
!7
Resolve "RETRACT dysfunctional"
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
build-envs/README
+7
-0
7 additions, 0 deletions
build-envs/README
with
7 additions
and
0 deletions
build-envs/README
+
7
−
0
View file @
0b9b10a3
...
...
@@ -25,6 +25,13 @@ Running things by hand
$ docker pull registry.gitlab.com/cerl/maestro/maestro-core/buildenv/debian
$ docker run --ulimit memlock=133000:133000 -i -t registry.gitlab.com/cerl/maestro/maestro-core/buildenv/debian /bin/bash
# but since you're reading this, you may be interested in debugging. In that
# case, to permit gdb to work inside the docker container you might want to
# use
# docker run --cap-add=SYS_PTRACE --ulimit memlock=133000:133000 -i -t registry.gitlab.com/cerl/maestro/maestro-core/buildenv/debian /bin/bash
# instead
# now you have a shell in the docker container that is currently used on gitlab for CI
$ mkdir /builds
$ cd /builds
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment