-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support specifying a user under which to run the container #135
Comments
nhavens
pushed a commit
to nhavens/tox-docker
that referenced
this issue
Jun 18, 2022
Username or UID to run commands as inside the container. https://docs.docker.com/engine/reference/run/#user Resolves tox-dev#135
nhavens
pushed a commit
to nhavens/tox-docker
that referenced
this issue
Jun 18, 2022
Username or UID to run commands as inside the container. https://docs.docker.com/engine/reference/run/#user Resolves tox-dev#135
tox-docker 4.1.0 added support to build & use a Dockerfile in the repo. Does the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'd like to be able to use
tox-docker
both to test via Jenkins as well as to test on my local machine.tox
will run as a different user in each of these environments. To get the correct file permissions on any files created on volume mounts, I'd like to be able to specify the user under which to run the container. Without this, when I volume mount the directory from whichtox
runs and any files get created by the container with root ownership (I'm running as root in the container), the next Jenkins job'sdeleteDir()
will fail with permission denied errors.The text was updated successfully, but these errors were encountered: