Closed petr-tik closed 6 years ago
Easiest fix is probably to roll back to previous LTS release of Ubuntu.
Don't we need the --cap-add
before the image name? I think Docker interprets everything after the image name as the command / arguments to run inside the container.
I've run into this problem recently with the -v
tag to mount volumes inside a container; it only works if it's specified before the image name.
docker run [OPTIONS] IMAGE[:TAG|@DIGEST] [COMMAND] [ARG...]
Sadly the Appveyor run takes so long that there's no point having it.
Sorry @petr-tik but I don't see any sense in merging this, no reflection on your fine investigation just that slow CI that brings us nothing is not worth fixing.
That's fine - this is a good case for the section.
Ideas that were considered and discarded
in the PR commit message
We have now learnt about docker restricting ptrace and it's importance to running ASAN -
As found on SO and docker documentation
https://stackoverflow.com/questions/49735926/address-sanitizer-with-gcc-fails-on-ubuntu-17-10-docker-container
https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities