On 20/04/2021 08:41, Giuseppe Scrivano wrote:

lejeczek via Podman <podman@lists.podman.io> writes:

...

Hi guys.

First thing which came to mind was to try driver newer version of the driver or newer kernel all together - when I got this upon container creation: .... overlayfs: unrecognized mount option "volatile" or missing value overlayfs: unrecognized mount option "volatile" or missing value what version of the kernel and podman are you using?

containers/storage checks internally for the "volatile" flag support in overlay but that should not be propagated to Podman when it fails.

How was the container created?

Giuseppe

podman version 3.1.0-dev 4.18.0-301.1.el8.x86_64 I'm on CentOS Steam. Actually, now I realize I see that pretty much with every podman's command executed. More specifically, those are kernel messages, podman says nothing, but I see, saw for the first time yesterady that staring some(all?) containers fails. So, I' testing it now: -> $ podman network create /etc/cni/net.d/cni-podman0.conflist -> $ podman network ls NETWORK ID    NAME         VERSION  PLUGINS 39e9c7a64c68  cni-podman0  0.4.0    bridge,portmap,firewall,tuning -> $ podman pod create --network cni-podman0 --hostname net-${HOSTNAME%%.*} --name net-${HOSTNAME%%.*} --publish 13000:3000 00bfa51e066fa7a069ad89d44bfa18184b0a31a0a41b9df2b24265f6e6d54ec5 # <- takes a few long seconds. -> $ podman run -d --restart=always --pod=net-${HOSTNAME%%.*} --name net-redis  -e ALLOW_EMPTY_PASSWORD=yes docker.io/bitnami/redis e11d2099d4452f95b0705802ceafcd189b52fdae546e92649ec04835ff11e35a That container above starts and produces logs. -> $ podman container rm --force net-redis e11d2099d4452f95b0705802ceafcd189b52fdae546e92649ec04835ff11e35a -> $ podman run -d --restart=always --pod=net-${HOSTNAME%%.*} --name net-redis  docker.io/discourse/base:2.0.20210217-2235 0e21bdf66c1cf99c1980b41952e9a2d3a223616718655cd560841ca155d74294 # !! <- this causes a local mayhem, overlayfs: unrecognized mount option "volatile" or missing value # logs every second and though podman says: -> $ podman container ls CONTAINER ID  IMAGE COMMAND   CREATED             STATUS PORTS                    NAMES 79d7f41fe9c7  registry.access.redhat.com/ubi8/pause:latest infinity  5 minutes ago       Up 4 minutes ago 0.0.0.0:13000->3000/tcp  00bfa51e066f-infra 0e21bdf66c1c  docker.io/discourse/base:2.0.20210217-2235 bash      About a minute ago  Up Less than a second ago 0.0.0.0:13000->3000/tcp  net-redis it's not possible to get net-redis' logs nor terminal-connect to it. -> $ podman exec -it net-redis sh Error: can only start exec sessions when their container is running: container state improper I'll share a thought - I realize we all push that CentOS Stream forward to be that bleeding edge for RHEL (since RedHat's announcement) if only ever so slightly, but as of now 'podman' does not look good on that CentOS. many thanks, L.

On 4/26/21 23:35, alexander.v.litvak@gmail.com wrote:

It doesn't fail but unrecognized mount option "volatile" or missing value appears with podman 3.1.2 on centos 7 with elrepo kernel 5.4.114-1.el7.elrepo.x86_64 #1 SMP Mon Apr 19 18:53:45 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux

It shows twice in journal upon running container overlayfs: unrecognized mount option "volatile" or missing value overlayfs: unrecognized mount option "volatile" or missing value

host: arch: amd64 buildahVersion: 1.20.1 cgroupManager: systemd cgroupVersion: v1 conmon: package: podman3-xcast-3.1.2-20210426221305.x86_64 path: /opt/podman/bin/conmon version: 'conmon version 2.0.27, commit: 65fad4bfcb250df0435ea668017e643e7f462155-dirty' cpus: 6 distribution: distribution: '"centos"' version: "7" eventLogger: journald hostname: web3n3-chi.siptalk.com idMappings: gidmap: null uidmap: null kernel: 5.4.114-1.el7.elrepo.x86_64 linkmode: static memFree: 3352928256 memTotal: 8350257152 ociRuntime: name: runc package: podman3-xcast-3.1.2-20210426221305.x86_64 path: /opt/podman/bin/runc version: |- runc version 1.0.0-rc93 spec: 1.0.2-dev go: go1.14.14 libseccomp: 2.5.1 os: linux remoteSocket: path: /run/podman/podman.sock security: apparmorEnabled: false capabilities: CAP_AUDIT_WRITE,CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_MKNOD,CAP_NET_BIND_SERVICE,CAP_NET_RAW,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT rootless: false seccompEnabled: true selinuxEnabled: false slirp4netns: executable: "" package: "" version: "" swapFree: 0 swapTotal: 0 uptime: 120h 46m 8.22s (Approximately 5.00 days) registries: search: - docker.xcastlabs.net - docker.io - quay.io store: configFile: /etc/containers/storage.conf containerStore: number: 1 paused: 0 running: 1 stopped: 0 graphDriverName: overlay graphOptions: overlay2.mountopt: nodev graphRoot: /var/lib/containers/storage graphStatus: Backing Filesystem: xfs Native Overlay Diff: "true" Supports d_type: "true" Using metacopy: "false" imageStore: number: 2 runRoot: /var/run/containers/storage volumePath: /var/lib/containers/storage/volumes version: APIVersion: 3.1.2 Built: 315532800 BuiltTime: Mon Dec 31 16:00:00 1979 GitCommit: 51b8ddbc22cf5b10dd76dd9243924aa66ad7db39-dirty GoVersion: go1.16 OsArch: linux/amd64 Version: 3.1.2

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 97070b707c36 docker.io/library/httpd:latest httpd-foreground 6 minutes ago Up 6 minutes ago 0.0.0.0:80->80/tcp gracious_ptolemy

_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io

When container storage is started, it is checkin whether the kernel on what options are supported, and the debug statement is showing that volatile mounting is not supported.