1.18.1 breaks podman --device

[svenstaro]

Hey, I'm not sure this is intended but I noticed that my services using --device stopped working with crun 1.18.1 (1.18.0 does work). I now get Operation not permitted, cannot open /dev/ttyUSB0 from my application when I do podman run ... --device /dev/ttyUSB0:/dev/ttyUSB0 ....

I think this is a regression as 1.18.1 specifically doesn't seem intend to break previous behavior (especially on cgroups v2).

Just to be super sure I checked podman info and it says cgroupVersion: v2.

[giuseppe]

no, it should not break.

Can you please share the command you've used to run podman?

[giuseppe]

nevermind, I guess a simple -device /dev/ttyUSB0:/dev/ttyUSB0 should do the trick. I'll check and let you know

[svenstaro]

Sure, this is straight from my zwavejsui.service systemd unit file which runs a Z-Wave JS UI container as root:

[Unit]
Description=Z-Wave JS UI
After=network-online.target

[Service]
Type=simple
Restart=on-failure
ExecStartPre=/usr/lib/systemd/systemd-networkd-wait-online
ExecStart=podman run \
  --name zwavejsui \
  --replace \
  --network slirp4netns:allow_host_loopback=true \
  --pull newer \
  --rm \
  --log-driver none \
  --device /dev/zwave:/dev/zwave \
  -v /var/lib/zwavejsui:/usr/src/app/store \
  -p 8091:8091 \
  -p 3000:3000 \
  docker.io/zwavejs/zwave-js-ui:latest
ExecStop=podman stop zwavejsui

[Install]
WantedBy=default.target

I realize this is kinda hard to test if you don't have that device node but maybe you can find a different device to pass through to a different image that's easier to test?

[giuseppe]

I'll cut a new release as soon as #1598 is merged