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
network name substitution #40819
Comments
Does is perport to support name substituion? In any case, docker-compose is in https://github.com/docker/compose, so closing this here. Please open on the compose repo with all the relevant details. Thanks! |
This is docker swarm problem in my case. |
Can you report to github.com/docker/cli? |
I think this should be possible already if you use the In that case, the name you reference the network as (within the stack) will be fixed, but the name of the actual network that's created will be customized. Something like this; networks:
mynetwork:
name: ${STAGE_NAME}
driver: bridge
ipam:
driver: default
config:
- subnet: ${STAGE_NETWORK_PREFIX}.0/24 Inside the compose file, you'd reference the network as "mynetwork", but |
network name substitution doesn't work in docker compose. see moby/moby#40819 (comment)
network name substitution doesn't work in docker compose. see moby/moby#40819 (comment)
network name substitution doesn't work in docker compose. see moby/moby#40819 (comment)
network name substitution doesn't work in docker compose. see moby/moby#40819 (comment)
network name substitution doesn't work in docker compose. see moby/moby#40819 (comment)
network name substitution doesn't work in docker compose. see moby/moby#40819 (comment)
network name substitution doesn't work in docker compose. see moby/moby#40819 (comment)
network name substitution doesn't work in docker compose. see moby/moby#40819 (comment)
network name substitution doesn't work in docker compose. see moby/moby#40819 (comment)
Network name substitution does not work.
Please, see details in:
https://devops.stackexchange.com/questions/6317/docker-compose-yml-make-network-name-configurable-via-environment-variable
The text was updated successfully, but these errors were encountered: