opening file `` for writing: No such file or directory: OCI not found

[doompadee]

/kind bug

After todays update (on Fedora 33) I'm no longer able to start my containers.

Trying with:

$ podman run --tz local --restart=always --pod podname --name mariadb \
-e MYSQL_USER=user \
-e MYSQL_ROOT_PASSWORD=rootpw \
-e MYSQL_PASSWORD=pw \
-e MYSQL_DATABASE=db \
-v /home/user/project/data/mariadb:/var/lib/mysql:Z \
-d docker.io/mariadb:10.5

yields:

ERRO[0000] error starting some container dependencies   
ERRO[0000] "opening file `` for writing: No such file or directory: OCI not found" 

Output of podman version:

podman version 3.2.0-rc1

Output of podman info --debug:

host:
  arch: amd64
  buildahVersion: 1.20.2-dev
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.0.27-2.fc33.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.27, commit: '
  cpus: 16
  distribution:
    distribution: fedora
    version: "33"
  eventLogger: journald
  hostname: aion
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 100
      size: 1
    - container_id: 1
      host_id: 165536
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1026
      size: 1
    - container_id: 1
      host_id: 165536
      size: 65536
  kernel: 5.11.17-200.fc33.x86_64
  linkmode: dynamic
  memFree: 4919390208
  memTotal: 32910745600
  ociRuntime:
    name: crun
    package: crun-0.19.1-2.fc33.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.19.1
      commit: 1535fedf0b83fb898d449f9680000f729ba719f5
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
  os: linux
  remoteSocket:
    path: /run/user/1026/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.1.9-1.fc33.x86_64
    version: |-
      slirp4netns version 1.1.9
      commit: 4e37ea557562e0d7a64dc636eff156f64927335e
      libslirp: 4.3.1
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.5.0
  swapFree: 21472407552
  swapTotal: 21474828288
  uptime: 118h 41m 14.42s (Approximately 4.92 days)
registries:
  search:
  - localhost
  - 127.0.0.1
  - registry.redhat.io
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - docker.io
store:
  configFile: /home/user/.config/containers/storage.conf
  containerStore:
    number: 2
    paused: 0
    running: 0
    stopped: 2
  graphDriverName: overlay
  graphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-1.5.0-1.fc33.x86_64
      Version: |-
        fusermount3 version: 3.9.3
        fuse-overlayfs: version 1.5
        FUSE library version 3.9.3
        using FUSE kernel interface version 7.31
  graphRoot: /home/user/.local/share/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  imageStore:
    number: 12
  runRoot: /run/user/1026/containers
  volumePath: /home/user/.local/share/containers/storage/volumes
version:
  APIVersion: 3.2.0-rc1
  Built: 1620248627
  BuiltTime: Wed May  5 23:03:47 2021
  GitCommit: ""
  GoVersion: go1.15.11
  OsArch: linux/amd64
  Version: 3.2.0-rc1

Package info:

podman-3.2.0-0.1.rc1.fc33.x86_64
crun-0.19.1-2.fc33.x86_64

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?

Yes

[Luap99]

Dup of #10274

[mheon]

Do you have the upstream testing repo enabled? This update should not have hit stable.

…

On Mon, May 10, 2021 at 10:21 Paul Holzinger ***@***.***> wrote: Dup of #10274 <#10274> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#10293 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3AOCFXQKACPHJ4MJTIL4LTM7TYDANCNFSM44RJM6CA> .

[doompadee]

@mheon No.

$ dnf repolist enabled
repo id                                                                      repo name
fedora                                                                       Fedora 33 - x86_64
fedora-cisco-openh264                                                        Fedora 33 openh264 (From Cisco) - x86_64
fedora-modular                                                               Fedora Modular 33 - x86_64
rpmfusion-free                                                               RPM Fusion for Fedora 33 - Free
rpmfusion-free-updates                                                       RPM Fusion for Fedora 33 - Free - Updates
tlp                                                                          tlp RPM packages
tlp-updates                                                                  tlp RPM packages
updates                                                                      Fedora 33 - x86_64 - Updates
updates-modular                                                              Fedora Modular 33 - x86_64 - Updates

It was surprising to receive an rc1...

[mheon]

Eeek. That’s not good.

…

On Mon, May 10, 2021 at 10:37 doompadee ***@***.***> wrote: @mheon <https://github.com/mheon> No. $ dnf repolist enabled repo id repo name fedora Fedora 33 - x86_64 fedora-cisco-openh264 Fedora 33 openh264 (From Cisco) - x86_64 fedora-modular Fedora Modular 33 - x86_64 rpmfusion-free RPM Fusion for Fedora 33 - Free rpmfusion-free-updates RPM Fusion for Fedora 33 - Free - Updates tlp tlp RPM packages tlp-updates tlp RPM packages updates Fedora 33 - x86_64 - Updates updates-modular Fedora Modular 33 - x86_64 - Updates It was surprising to receive an rc1... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10293 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3AOCCJDXDXNEL3AVB5OTLTM7VSRANCNFSM44RJM6CA> .

[Luap99]

I can confirm I just run dnf update and it wants to update to 2:3.2.0-0.1.rc1.fc33

[ma3yta]

already 2 days we have a broken release candidate in stable repo fedora-silverblue/issue-tracker#168

[mheon]

@rhatdan @vrothberg @lsm5 This is a rather large problem, the RC is definitely unstable and needs to be pulled.

…

On Mon, May 10, 2021 at 10:44 Paul Holzinger ***@***.***> wrote: I can confirm I just run dnf update and it wants to update to 2:3.2.0-0.1.rc1.fc33 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10293 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3AOCC4H6PGDPEDY2QTL23TM7WLLANCNFSM44RJM6CA> .

[doompadee]

I downgraded to 3.1.2 and things are working fine again. Would have been nice if dnf history undo last worked. It was surprisingly hard to find the packages online to downgrade manually. https://koji.fedoraproject.org/ turned out to be the lifesaver (although I could not find podman-docker there, but I don't really need it)