Make docker-compose not rely on local volumes #144

Closed
opened 2025-12-29 15:35:17 +01:00 by adam · 1 comment
Owner

Originally created by @ChristianKniep on GitHub (Jul 4, 2016).

When deploying the docker-compose file on a remote SWARM cluster it (most likely) won't have access to the github repository, hence the default config can not be mapped into the container.
I reckon that either the config is backed into the original container (while volumes_from) could be used by the nginx container or the config is derived from a template (confd/consul-template/...) using environment variables.

I'll try to provide a version that could be deployed remotely, not sure when I'll find the time.

Originally created by @ChristianKniep on GitHub (Jul 4, 2016). When deploying the docker-compose file on a remote SWARM cluster it (most likely) won't have access to the github repository, hence the default config can not be mapped into the container. I reckon that either the config is backed into the original container (while volumes_from) could be used by the nginx container or the config is derived from a template (confd/consul-template/...) using environment variables. I'll try to provide a version that could be deployed remotely, not sure when I'll find the time.
adam closed this issue 2025-12-29 15:35:17 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jul 7, 2016):

Closing because I think this was resolved by merging #188. If not, please reply and I'll reopen.

@jeremystretch commented on GitHub (Jul 7, 2016): Closing because I think this was resolved by merging #188. If not, please reply and I'll reopen.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#144