testcontainers / testcontainers/testcontainers-java
[Enhancement]: Create volumes for testcontainers
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
Proposal
I recently needed to create two test containers that shared data storage. One container would generate data, and the second would read this data. My first thought was to create a docker volume and share the volume in the two containers. This avoids bind mounts which complicates things greatly. Bind mounts are harder to make work cross platform and there are restrictions on bind mounts when I run in my CI tool, bitbucket pipelines.
However, I cannot find any way to do this with testcontainers. There is a way to use withVolumesFrom but there is no way to create the volume as best I can tell. Here is an example of what I was trying to do with test containers but shown with docker commands.
Create a first container with a annonymous volume:
docker run -it --rm --name source --volume=/share ubuntu bash
Create a second container that uses the same volume from the first:
docker run -it --rm --volumes-from source --name dest ubuntu bash
Then in the source container I write a file into the /share directory and I can cat it out in the dest container. I would like to set this up using test containers.
Thanks for this great tool!
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 in the Core module by tracing the existing withVolumesFrom support and the container configuration APIs. Compare them with Docker's volume and --volumes-from behavior described in the issue. Done means users can create a volume and share it between two test containers so data written by one can be read by the other.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100