Dynamically updating etchosts
Pro Tip: If you’re referring to women as sluts, hoes or other colorful insults because they’re not fucking you, you’re pretty much giving up the right to call yourself a nice guy.
If you’re carrying around a lot of anger at being single, then you need to learn to offload it.
And, considering the restrictions, this would also mean that containers started with the same name should get the same docker IP address (at least as long as someone is linking to them). Although I understand service-discovery systems can be used, it does require more knowledge and setting-up than simple links.
Everybody’s physique is going to be different and fit is going to mean very different things to different people.An ambassador container could either provide dynamic routing based on some service discovery like described here: Or a simple socat which would have to be restarted in-place and therefor depends on #2733 There is actually a use case not covered by #2733 - what if I want to completely change the linked container, for example I have a service that is started with a local Redis container and I want to replace that with an ambassador that points to a remote Redis.To allow for that we would want the linking to be name based.You should be able to delete the database container and start a new one with the same name and have links re-established when you restart the client [email protected] but is it the same container, or a new container (with the same name)?