stable

podman-3.2.0-0.1.rc1.fc34

FEDORA-2021-fc15685f73 created by rhcontainerbot 3 years ago for Fedora 34

Autobuilt v3.2.0-rc1

How to install

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-2021-fc15685f73

This update has been submitted for testing by rhcontainerbot.

3 years ago

This update's test gating status has been changed to 'failed'.

3 years ago

This update's test gating status has been changed to 'waiting'.

3 years ago

This update's test gating status has been changed to 'failed'.

3 years ago

This update has been pushed to testing.

3 years ago

This update's test gating status has been changed to 'passed'.

3 years ago

lsm5 edited this update.

3 years ago
User Icon lsm5 commented & provided feedback 3 years ago
karma

podman run -it fedora bash doesn't give me a container shell. It's waiting endlessly, and also causes other processes to wait until I manually kill podman.

User Icon nickavem commented & provided feedback 3 years ago
karma

Seems generally functional. Also, happy to find docker-compose now works rootless with docker-compose -H unix:/run/user/1000/podman/podman.sock

User Icon lsm5 commented & provided feedback 3 years ago
karma

hmm, seems to work fine now. Maybe something on my end. Revising karma.

This update can be pushed to stable now if the maintainer wishes

3 years ago
User Icon andilinux commented & provided feedback 3 years ago
karma

works for me

User Icon dustymabe commented & provided feedback 3 years ago
karma

though I suspect we're not sending an rc to stable, which I think is correct.

This update has been submitted for stable by rhcontainerbot.

3 years ago
User Icon ersen provided feedback 3 years ago
karma

This update has been pushed to stable.

3 years ago
User Icon ma3yta commented & provided feedback 3 years ago
karma

unable to start container after update https://github.com/containers/podman/issues/10274

User Icon nomadicbits commented & provided feedback 3 years ago
karma

Seeing the same on stable F34, Systemd files unable to start containers

User Icon harryc commented & provided feedback 3 years ago
karma

unable to start container after update (OCI not found)

User Icon ma3yta provided feedback 3 years ago
karma
User Icon pnemade commented & provided feedback 3 years ago
karma

It is really bad for Silverblue users to have broken toolbox after upgrade. I don't understand why rhcontainerbot is used for stable releases. Let it play whatever that bot want in rawhide but please check thoroughly before pushing any update to stable releases. For podman updates really why autopush is by default enabled? It MUST be manually pushed to stable by update submitter which should be real person. I wonder what kind of testing has been done by +ve karma submitters here which all of other user's simple toolbox start test failure cannot be captured in their testing. Please don't push podman releases like this to stable. Make toolbox start test mandatory to pass podman CI.

The toolbox start fails with below messages DEBU[0000] Initializing event backend journald
DEBU[0000] configured OCI runtime runc initialization failed: no valid executable found for OCI runtime runc: invalid argument DEBU[0000] configured OCI runtime kata initialization failed: no valid executable found for OCI runtime kata: invalid argument DEBU[0000] configured OCI runtime runsc initialization failed: no valid executable found for OCI runtime runsc: invalid argument DEBU[0000] Using OCI runtime "/usr/bin/crun"
DEBU[0000] Default CNI network name podman is unchangeable INFO[0000] Setting parallel job count to 25

User Icon laolux commented & provided feedback 3 years ago
karma

What about retracting this update? As is, it is still in stable, so when I run dnf update or dnf distrosync, this version of podman will get installed. Very annoying, because now I need to blacklist podman from updates, so that all other system updates can run through.


Please login to add feedback.

Metadata
Type
bugfix
Karma
0
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
3 years ago
in testing
3 years ago
in stable
3 years ago
modified
3 years ago

Automated Test Results