Automatic update for podman-5.3.0~rc1-1.fc41.
* Tue Oct 22 2024 Packit <hello@packit.dev> - 5:5.3.0~rc1-1
- Update to 5.3.0-rc1 upstream release
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2024-50c8b12d3cPlease login to add feedback.
This update's test gating status has been changed to 'waiting'.
This update has been submitted for testing by bodhi.
packit edited this update.
This update's test gating status has been changed to 'failed'.
This update has been pushed to testing.
Works
works for me
works for me
FYI, stable by karma and time will be kept disabled on this one until we release 5.3.0.
packit edited this update.
New build(s):
Removed build(s):
Karma has been reset.
packit edited this update.
packit edited this update.
packit edited this update.
packit edited this update.
packit edited this update.
This update has been submitted for testing by bodhi.
This update has been pushed to testing.
Work well but i have a bug when i try podman machine start Starting machine "podman-machine-default" ERRO[0000] process 39675 has not ended
Error: failed to find virtiofsd: exec: "virtiofsd": executable file not found in $PATH
packit edited this update.
New build(s):
Removed build(s):
Karma has been reset.
packit edited this update.
packit edited this update.
packit edited this update.
packit edited this update.
packit edited this update.
This update has been submitted for testing by bodhi.
This update has been pushed to testing.
james@a5:~$ podman machine start Starting machine "podman-machine-default" ERRO[0000] process 5537 has not ended
Error: failed to find virtiofsd: exec: "virtiofsd": executable file not found in $PATH james@a5:~$ echo $PATH /home/james/.local/bin:/home/james/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin james@a5:~$ export PATH=$PATH:/usr/libexec james@a5:~$ echo $PATH /home/james/.local/bin:/home/james/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/usr/libexec james@a5:~$ podman machine start Starting machine "podman-machine-default"
This machine is currently configured in rootless mode. If your containers require root permissions (e.g. ports < 1024), or if you run into compatibility issues with non-podman clients, you can switch using the following command:
Mounting volume... /home/james:/home/james API forwarding listening on: /run/user/1001/podman/podman-machine-default-api.sock You can connect Docker API clients by setting DOCKER_HOST using the following command in your terminal session:
Machine "podman-machine-default" started successfully james@a5:~$ rpm -qa podman podman-5.3.0~rc3-1.fc41.x86_64
SO IT WORK !!!!
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
packit edited this update.
New build(s):
Karma has been reset.
packit edited this update.
packit edited this update.
packit edited this update.
packit edited this update.
packit edited this update.
This update has been submitted for testing by bodhi.
packit edited this update.
New build(s):
Karma has been reset.
This update has been pushed to testing.
packit edited this update.
New build(s):
Removed build(s):
Karma has been reset.
packit edited this update.
packit edited this update.
packit edited this update.
packit edited this update.
packit edited this update.
This update has been submitted for testing by bodhi.
nsella edited this update.
This update's test gating status has been changed to 'waiting'.
nsella edited this update.
This update's test gating status has been changed to 'failed'.
This update has been pushed to testing.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Hi, can you folks (who added karma here) test again with the final builds here and add the karma again so we can get this into stable please. Thank you.
LGTM. One test failure which I'm 99% certain is a bug in the test itself.
Works for me.
This update can be pushed to stable now if the maintainer wishes
Works for me , generally functional
This update has been submitted for stable by bodhi.
This update has been pushed to stable.