![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
2·
4 months agoThis was a fast response, and doesn’t cover the whole scope of handling networking in docker. As mentioned elsewhere there is a different network philosophy for Standalone Containers & Overlay networking.
This was a fast response, and doesn’t cover the whole scope of handling networking in docker. As mentioned elsewhere there is a different network philosophy for Standalone Containers & Overlay networking.
You declare the ip in your setup, or in the yaml file. An example for the docker-compose file is in the link below. I’d expect you’ll want to declare the network and such as well, if you’re not familiar.
https://gist.github.com/natcl/3d881d00a56c8a961e6dab8ba51a5a37
Not to be pedantic, commercial systems do go through lock replacements if they are budgeting properly.
A guest wouldn’t notice unless they were watching maintenance teams replacing lock internal components.