testcontainers / testcontainers/testcontainers-java
GenericContainer withFileSystemBind: creates a root owned directory/file
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
Module
Core
Testcontainers version
1.19.8
Using the latest Testcontainers version?
Yes
Host OS
Ubuntu 22.04.4 LTS
Host Arch
x86
Docker version
26.1.4
What happened?
Using the following statement:
new GenericContainer<>("...")
...
.withFileSystemBind("...", "...", BindMode.READ_WRITE)
...;
creates a root:root directory/file while executed by a normal, non-root user.
Is there any way to avoid that and to create directories/files owned by the current user ?
Relevant log output
No response
Additional Information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at GenericContainer.withFileSystemBind and reproduce the READ_WRITE bind on Ubuntu 22.04.4 with Docker 26.1.4, checking how the root-owned directory or file is created. Done means establishing whether ownership can follow the current non-root user and verifying the behavior with a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100