5:39 a.m.
On 10/05/2022 09:30, Giuseppe Scrivano wrote:
Was the container created with `--privileged`?
Could you try with the fix proposed here:
https://github.com/containers/podman/issues/11239#issuecomment-940885242
Thanks
lejeczek via Podman <podman(a)lists.podman.io> writes:
> Hi guys
>
> I get this, with I think is really weird and I hope somebody could
> shed more light on it.
>
> -> $ podman container restart wordpress.test.bits
> Error: crun: error stat'ing file `/dev/bus/usb/001/003`: No such file
> or directory: OCI runtime attempted to invoke a command that was not
> found
>
> There is only one USB I can guess is in play - an USB NIC but it has
> nothing to do with podman container nor its networks.
>
> But I also get this (different host from above):
>
> -> $ podman container restart wordpress.test.bits
> Error: crun: error stat'ing file `/dev/fb0`: No such file or
> directory: OCI runtime attempted to invoke a command that
> was not found
>
> What is podman/crun doing there & why?
> v 4.0.3
> many thanks, L.
> _______________________________________________
>
Yes '--privileged' was used.
Seems that 'stating' error can regard any 'device'. Such an
error podman will report after host reboot:
-> $ podman container restart wordpress.test.bits
Error: crun: error stat'ing file `/dev/tap36`: No such file
or directory: OCI runtime attempted to invoke a command that
was not found
-> podman run -dt --log-driver k8s-file --publish
127.0.0.1:2081:80 --restart=always --privileged
--security-opt label=disable --volume ...
Above is how I set my containers - I do not point to any
device, do not use '--device=' with 'run' at all - which
container works fine, until next OS re/boot.
Thus, fix you suggest - still worth trying?
thanks, L.
p.s. Giuseppe, follow etiquette and rules - it's english
lang and mailing list so it's not conversation just between
two of us - so do go, from top down