[Request]: Add Command To Update Container Configuration

[Mcrich23]

Feature or enhancement request details

As I build compose for container (see #239), it has become very clear that Container needs some form of a command to update a container without entirely removing the container, because it can cause issues with things such as ip addresses.

Thoughts?

Code of Conduct

• I agree to follow this project's Code of Conduct

[keys-i]

Yeah, makes sense. Recreating containers just to tweak something can be annoying, especially when IPs change and mess with networking. An update command would be super handy. Definitely worth looking into.

[jglogan]

because it can cause issues with things such as ip addresses

@Mcrich23 Can you describe a few scenarios where you this is necessary? IP addresses aren't part of the container configuration; they're assigned on the fly. I'd think that a compose-like orchestrator would prefer to have containers address each other via DNS names instead of addresses.

Another thing to consider is starting a discussion where you can describe your design. For a compose that supports multiple networks (say, frontend and backend networks for a three tier setup), this might help us all work out what sorts of enhancements are necessary. At the level of individual issues like this it's hard to understand how everything should fit together.

[Mcrich23]

No problem @jglogan! I can do this tomorrow. I am currently working on refactoring my compose tool to use internal tools instead of calling the shell environment, but will do this when I have a better idea.

I have already handled IP Addresses between containers, but development can be rough if an app depends on a constant local ip and it changes on each container run.

[Mcrich23]

@jglogan #320