Our tests used to pass but now we get: WARNING: Your kernel does not support memory swappiness capabilities, memory swappiness discarded. and errors regarding containers like: Error response from daemon: Cannot destroy container 0478e4cd1888fc63db7992119a815b022e8a29484ce1966de6723b71a25e762a: Dr…

I have more details about the issue. The docker is being executed with all the security constraints: docker run --net=none --privileged=false --cap-drop=ALL -t --entrypoint=bash “codacy-eslint:latest” After some more testing, I found that --cap-drop=ALL might be the problem. Inside the docker in…

I don’t think I have any insight into this right now. Does the same operation succeed if you omit the --cap-drop=ALL part?

It works without --cap-drop=ALL, but the whole point to test in circleCI is to make sure it works in the same conditions of our production environment… Can you have someone look into this?

The behavior that you are seeing seems to be correct for me. When -cap-drop=ALL is specified, user creation should fail. Although it behaves slightly different, I also get an somewhat error when running the following command locally. docker run --cap-drop=ALL ubuntu /bin/sh -c "useradd -m -p encry…

Failing Tests using Dockers in CI

Build Environment

levlaz November 26, 2015, 5:00am 2

This is a known issue, it is addressed here.

Topic		Replies	Views
Docker: setup user operation not permitted Build Environment docker	1	3137	April 4, 2016
Unable to run Docker in Docker in CircleCI Build Environment docker	0	2204	May 19, 2016
Error removing intermediate container during Docker build Build Environment docker	1	4821	April 7, 2016
Original error: CircleCI was unable to start the container because of a userns remapping failure in Docker Build Environment docker	2	1051	December 19, 2022
Kitchen Docker Builds Fail when using Privileged Containers Build Environment docker	2	3412	May 18, 2017

Failing Tests using Dockers in CI

Related topics