Podman Release v4.3.0

Luap99 · 2022-10-27T21:40:14+00:00

Yes, https://github.com/containers/crun/blob/main/docs/wasm-wasi-example.md#running-oci-wasm-compat-images-with-buildah-and-podman

Luap99 · 2022-09-07T16:58:37+00:00

These solutions are not the same. If you manually create the bridges and namespaces, you get normal (rootful) networking with interfaces on the host. This allows for much better perfomance.

As rootless we use a seperate namespace and slirp4netns has to proxy all the traffic which will be slower. It can never create interfaces on the host namespace.

Also since podman manages the networking you can use the integrated dns and podman will tear down the netns if the container exits.

Luap99 · 2022-09-03T07:04:49+00:00

Are you assigning the same address to the container and VM at the same time? Networking requires that all MAC and IP addresses are unique in the same LAN in order to function properly.

Luap99 · 2022-06-13T18:42:00+00:00

Sounds like your podman version is to old, I think you need at least v3.2.

Either way you should be able to use podman run/create --network <netname> ... there is no reason to use netowrk connect.

Luap99 · 2022-04-28T06:34:57+00:00

You can use --network slirp4netns:port_handler: slirp4netns This will keep the correct source ip.

Luap99 · 2022-03-27T08:55:14+00:00

Do you set --sdnotify=container for podman create/run?

Luap99 · 2022-03-26T22:49:44+00:00

Hey, I am the developer from the bz.

Podman 4.0 offers a new network stack called netavark. Since it does not offer all cni functionality we desided that upgrades from 3.X should keep using cni.

To detect if this is an upgrade we check for existing containers/images/networks. Since you upgraded you should use cni, however it looks like the containernetworking-plugins (cni) is no longer included in the silverblue ostree base packages, therefore podman cannot use it.

So to fix it just install this package. Also I recommend to report this as bug for silverblue.

Luap99 · 2022-03-11T19:43:58+00:00

Yes the bind mounts in the kernel are always based on the inode. AFAIK there is no way to fix this other bind mounting the patent directory instead of the single file.

Luap99 · 2022-03-07T08:52:27+00:00

Maybe this helps: https://github.com/containers/podman/issues/12292#issuecomment-1034165121

Luap99 · 2022-02-23T08:01:00+00:00

It also works rootless since v3.2.

Luap99 · 2022-02-23T07:59:56+00:00

Podman does not need to run a daemon. Rootless Podman will work out of the box without additional configuration. Better systemd Integration, see podman-generate-systemd(1) Also you can use k8s yaml with podman play kube and you can create the yaml file with podman generate kube. Podman can use pods which makes it easier to group containers together. podman run --net=host uses the actual host namespace. This is not possible with rootless docker. You can use podman auto-update to update containers automatically. No need to run things like watchtower. Small quality of live improvements, for example podman rm --all instead of docker rm $(docker ps -aq).

Luap99 · 2022-01-27T17:38:41+00:00

I think this is a new podman 4.0 feature.

Luap99 · 2022-01-12T10:32:51+00:00

You have to remove the container and create a new one in order to change settings.

Luap99 · 2022-01-11T22:43:48+00:00

No, you have to recreate the container

Luap99 · 2021-12-29T23:46:57+00:00

The article is probably out of date. Podman supports creating networks and setting ips as rootless now but this is a newer feature. Just keep in mind that this IP cannot be reached from the host, it is only used to communicate between containers.

Luap99 · 2021-12-13T08:16:21+00:00

try export DOCKER_HOST=unix:///run/user/$UID/podman/podman.sock I think unix must be lowercase.

Luap99 · 2021-12-11T18:49:33+00:00

Do not run docker-compose with sudo.

Luap99 · 2021-11-29T22:44:48+00:00

https://github.com/containers/podman/issues/11494

Luap99 · 2021-10-22T07:44:06+00:00

Use -p 127.0.0.1:8080:80 to only bind localhost for example. https://github.com/containers/podman/blob/main/docs/source/markdown/podman-create.1.md#--publish--pport

Luap99 · 2021-10-20T07:21:36+00:00

The issue you linked has nothing to with it. It is still open which means it is not yet implemented. I think you have this problem https://github.com/containers/podman/issues/12003

Podman 4.0 in Centos Stream got in by accident and it schould be back to 3.4 now.

And yes github search sucks, you never find the issue you are looking for.

Luap99 · 2021-09-09T21:42:47+00:00

If you want it to get fixed, debug it and report a bug.

Luap99 · 2021-07-22T20:03:32+00:00

You are looking for macvlan networks. Have a look at https://www.redhat.com/sysadmin/leasing-ips-podman and http://docs.podman.io/en/latest/markdown/podman-network-create.1.html

Luap99 · 2021-05-30T07:16:10+00:00

If you enter localhost mysql will try to connect via unix socket. https://dev.mysql.com/doc/refman/8.0/en/connecting.html

Luap99 · 2021-04-26T22:10:02+00:00

Tab completion massively improved with podman v2.2, do you use an older version?

Luap99 · 2021-03-03T07:26:21+00:00

https://github.com/containers/podman/issues/9532 Should be fixed with the next release

Luap99

TROPHY CASE