Support static network configurations

[containers]

Support static network configurations

[muayyad-alsadi]

Does this work rootless? What are podman commands to do this?

I guess one need root privilege to create a bridge via brctl and also need root privildge to create veth pair and configure themm. Which I guess rootless podman can't do.

Docker can do that because it's talking to a root daemon which is something bad we are trying to avoid.

Not sure if this works in a rootless way. Without this, networks are created automatically per container "group" (i.e. per docker-compose file, such as is the case now) and with this, the network that is created is statically set and the IP addresses per container are as well, so I think (but am not sure) that static networks don't need any extra privileges, but I may be wrong.

Another problem that you may run into, though, is that this particular image wants to open the SMTP and HTTP ports in the container, which are ports below 1024, which probably require root. I get errors if I don't start this with root (even without the static networks). This sounds strange since these ports are not being opened on the host, but on the container (and not even mapped on the host), but that may be a problem or limitation of Podman itself.

[muayyad-alsadi]

SMTP and HTTP ports in the container, which are ports below 1024, which probably require root.

this is not a problem because you can be root inside container without being root in the host.

here is an example

$ podman run -d  -p 8080:80 -w /var/www/html busybox /bin/busybox httpd -h . -f -p 80

here httpd inside the container opened port 80 because it's root inside the container.

Thanks for the tip. This makes it even more strange as I cannot currently use Podman to start the example container without using sudo, even if I remove the static networks.

Could this have something to do with the network type used (e.g. 1podfw)?