-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
podman: broken network functionality for CNI plugins #7753
Comments
interesting. do you think it makes sense to add the following to image testing ?
|
btw, is it possible to downgrade podman using apt-get ? it would help to unblock users before podman fix is released |
I just realized that I was doing "sudo apt-get update && sudo apt-get -y install podman" . If I remove this line, the issue is not happening. I think by running apt-get I was installing the latest podman version, which is the broken one. I did not know the base image contained podman. Thus, by not running the apt-get command it works... but we do not have the latest updates from podman. However, it will buy us some time, at least until it is fixed in Ubuntu. |
it is similar to what we do during image generation. thus we could deploy buggy podman. we test podman, but just "podman -v" |
There is a regression in podman that fails to create networks. The workaround is to avoid update of the podman package. We can skip the installation since both podman and docker-compose are available in the base image. See: actions/runner-images#7753
There is a regression in podman that fails to create networks. The workaround is to avoid update of the podman package. We can skip the installation since both podman and docker-compose are available in the base image. See: actions/runner-images#7753
There is a regression in podman that fails to create networks. The workaround is to avoid update of the podman package. We can skip the installation since both podman and docker-compose are available in the base image. See: actions/runner-images#7753
There is a regression in podman that fails to create networks. The workaround is to avoid update of the podman package. We can skip the installation since both podman and docker-compose are available in the base image. See: actions/runner-images#7753
There is a regression in podman that fails to create networks. The workaround is to avoid update of the podman package. We can skip the installation since both podman and docker-compose are available in the base image. See: actions/runner-images#7753
Unfortunately the workaround does not work anymore in 20230619.1.0, it worked in 20230611.1. |
I can imagine that |
@jordimassaguerpla , can you please help with podman ? is it possible to make it return non zero ? |
There is a regression in podman that fails to create networks. The workaround is to avoid update of the podman package. We can skip the installation since both podman and docker-compose are available in the base image. See: actions/runner-images#7753
There is a regression in podman that fails to create networks. The workaround is to downgrade the podman package. See: actions/runner-images#7753
|
yes, that was an example. the exact command may be constructed from launchpad issue which describes known working version
|
@jordimassaguerpla , can you please review 43936f0 ? |
There seems to be an issue with Podman (libpod specifically) on Ubuntu 22.04, which might affect networking. See [1] and [2] [1] actions/runner-images#7753 [2] https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/2024394
…tests (#6928) * WIP: check Podman version * wip: try the workaround suggested in [1] There seems to be an issue with Podman (libpod specifically) on Ubuntu 22.04, which might affect networking. See [1] and [2] [1] actions/runner-images#7753 [2] https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/2024394
Done. Sorry I could not do it last week. |
Workaround included into the image |
Description
Since yesterday, I see this error
I believe is a bug in the latest ubuntu update of podman https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/2024394
Platforms affected
Runner images affected
Image version and build link
?
Is it regression?
yes
Expected behavior
2 days ago I had no error and network was working as expected with podman rootfull.
Actual behavior
Network does not work see https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/2024394
Repro steps
podman network create -d bridge test-net
podman network ls
The text was updated successfully, but these errors were encountered: