Skip to content
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

Docker compose support #25

Closed
mraerino opened this issue Nov 22, 2018 · 3 comments · Fixed by #97
Closed

Docker compose support #25

mraerino opened this issue Nov 22, 2018 · 3 comments · Fixed by #97

Comments

@mraerino
Copy link
Contributor

The java implementation supports spinning up docker compose setups to test larger setups as a black box.

This is interesting for this library especially since many DevOps people are using Golang for their services anyways.

@mdelapenya
Copy link
Collaborator

Is there a plan to work on this? I'd be willing to help in this efforts if possible

@gianarb
Copy link
Collaborator

gianarb commented Sep 10, 2019 via email

@mdelapenya
Copy link
Collaborator

mdelapenya commented Sep 10, 2019

Yeah, I'm currently playing around with the local docker compose implementation (no socat)

mdelapenya referenced this issue in mdelapenya/testcontainers-go Sep 11, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Sep 11, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Sep 11, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Sep 11, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Sep 11, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Sep 11, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Sep 18, 2019
We need to add compose-specific environment variables for identifier
and compose file path
mdelapenya referenced this issue in mdelapenya/testcontainers-go Sep 18, 2019
We reuse it in the first test, checking that the env variable is not set
mdelapenya referenced this issue in mdelapenya/testcontainers-go Sep 18, 2019
It is shared by invoke and down
mdelapenya referenced this issue in mdelapenya/testcontainers-go Sep 18, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Sep 18, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Sep 18, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Oct 29, 2019
It could disclose environment variables
mdelapenya referenced this issue in mdelapenya/testcontainers-go Nov 18, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Nov 18, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Nov 18, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Nov 19, 2019
I'm not adding information about the environment to avoid disclosing
sensible values, but it could be easily added
mdelapenya referenced this issue in mdelapenya/testcontainers-go Nov 19, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Nov 19, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Nov 20, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Nov 22, 2019
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
We need to add compose-specific environment variables for identifier
and compose file path
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
We reuse it in the first test, checking that the env variable is not set
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
It is shared by invoke and down
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
It could disclose environment variables
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
I'm not adding information about the environment to avoid disclosing
sensible values, but it could be easily added
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
It was just a matter of setting the container name at docker-compose
level, because we just want to access the container to read its
environment variables and do some calculations with them.
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
mdelapenya referenced this issue in mdelapenya/testcontainers-go Apr 16, 2020
gianarb added a commit that referenced this issue Apr 20, 2020
(#25) Create very basic implementation of Local Docker Compose
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants