You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I apologize if there is already a request with this meaning, but I will be very happy if cockpit-podman will support assigning a static IP address to the container..
I don't know or work with podman much, but I found on Google that a static IP address can be assigned to a container using the --ip argument in the run?
That feature is indeed missing, overall configuration of networking is kinda lacking in cockpit-podman. We probably want to introduce a new tab "networking" with more networking related options when creating a new container or pod.
Hi! If the "networking" tab backlog is still open for ideas, it would also be nice to be able to select the network for binding the container: bridge by default, but also host, none, or one of the custom ones defined. Host would not require any port mapping.
Hi,
I apologize if there is already a request with this meaning, but I will be very happy if cockpit-podman will support assigning a static IP address to the container..
I don't know or work with podman much, but I found on Google that a static IP address can be assigned to a container using the --ip argument in the run?
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/building_running_and_managing_containers/assembly_setting-container-network-modes_building-running-and-managing-containers
So if this static IP address could be set via cockpit-podman in container, that would be fine. :-) Thanks
The text was updated successfully, but these errors were encountered: