On 13/04/2022 14:43, Daniel Walsh wrote:
On 4/13/22 09:08, Barry Scott wrote:
> The OS is oracle linux 8 with
>
> podman-3.4.2-9.0.1.module+el8.5.0+20494+0311868c.x86_64
> kernel-4.18.0-348.20.1.el8_5.x86_64
>
> I start a container in a systemd service using:
>
> + /usr/bin/podman start cloud-dice
>
> And get this error from podman:
>
> Error: unable to start container
> "76e4a2480bc7f81d3baa802f3d48fffc2e3d252a52f33039d83e339d3f158532":
> failed to mount shm tmpfs
>
"/var/lib/containers/storage/overlay-containers/76e4a2480bc7f81d3baa802f3d48fffc2e3d252a52f33039d83e339d3f158532/userdata/shm":
> invalid argument
>
> And these messages in dmesg:
>
> [82521.621247] tmpfs: Unknown parameter 'context'
> [82521.643785] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [82521.648888] IPv6: ADDRCONF(NETDEV_UP): vethc149f6ee: link is not
> ready
> [82521.650561] IPv6: ADDRCONF(NETDEV_CHANGE): vethc149f6ee: link
> becomes ready
> [82521.651950] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> [82521.654408] cni-podman0: port 1(vethc149f6ee) entered blocking state
> [82521.655364] cni-podman0: port 1(vethc149f6ee) entered disabled state
> [82521.656594] device vethc149f6ee entered promiscuous mode
> [82521.657537] cni-podman0: port 1(vethc149f6ee) entered blocking state
> [82521.658455] cni-podman0: port 1(vethc149f6ee) entered forwarding
> state
> [82521.880289] cni-podman0: port 1(vethc149f6ee) entered disabled state
> [82521.883696] device vethc149f6ee left promiscuous mode
> [82521.884435] cni-podman0: port 1(vethc149f6ee) entered disabled state
>
> If I rebuild the container then I do not see the tmpfs error and
> everything works.
>
> What do I need to do to fix the "tmpfs: Unknown parameter
'context'"
> error that I'm assuming is root cause?
>
> Barry
>
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io
context seems to be an SELinux thing. Did you create a machine with
SELinux and then reboot with it disabled?
Yes that looks like the cause. We use puppet to config the machine and
it has a rule that disabled selinux.
I take it that selinux must be in the same state for the creation of the
container and when it is started?
Barry
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io