Docker design questions - 4.14.1+ #2159
Replies: 2 comments
-
|
You could even automate the internal cert creation process based off network info provided in the compose file, as well as set the info in the config files rather than them being hardcoded the way they are currently. I had to manually change several entries to get it to work using - instead of . in the names, including for the certs themselves. I've got this working so far, but it's a WIP. Was having issues with assigning IPs... because they were probably hardcoded to use 0.0.0.0 in the config files. I'll take a look at that. docker-compose .env Assumes default users and passwords |
Beta Was this translation helpful? Give feedback.
-
|
It looks like you're addressing some of the things I mentioned in 5.0.0, but some things still are problematic. I forked the repo and I'm working on updating the compose files for consistency (structure and naming) and proper networking, removing the . in the names of the services, hostnames, etc, and having them be set by env variables, which makes updating things much easier on the dev side and also allows for a little flexibility. Ideally a nginx container would serve as proxy for all ingress and egress, with the other containers only on a backhaul network, but I suck at nginx configuration as I've worked with it for about 1 hr total. I've got a workaround in place, but it's not ideal. If I can figure out the workings, I'm going to also try to get references to the hostnames/nodes to be set via env at first run, and have the certs generate at first run, also based on the env variables, again for consistency in naming and to avoid the . in the names issue. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What is the purpose of using intercontainer certificates rather than an internal only network with nginx serving as the single point of ingress with custom certs/letsencrypt that connects to both the internal network and a bridge net?
I see that you're pulling the cert generator live, which is a break from best practices if I'm not mistaken.
I've also seen several projects recently that require pulling the project files, like this one, which also seems a bit odd to me. Theoretically you shouldn't need to do anything except possibly create a few folders on the host and create/edit the docker-compose and env files.
I'm still digging through files and trying to understand some of the decisions made, so forgive me if I've missed something obvious. I'm just starting to delve into actually creating docker images, so it could just be that I'm not up to speed on current standards.
Beta Was this translation helpful? Give feedback.
All reactions