Feature or enhancement request details

Currently, containers launched via the container CLI do not offer a way to define or control their IP address. This limits flexibility in several use cases, including:

• Local development scenarios that rely on predictable container IPs
• Inter-container communication, where fixed IPs are preferable
• Integration with tools or services expecting specific network behavior
• Testing network-related functionality that depends on a deterministic IP setup

While --network allows attaching to a custom network, it doesn't currently support IP address assignment or any advanced networking options.

Proposed Solution

Introduce an additional flag to container run, such as:

--ip <ip-address>

Code of Conduct

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