podman "Cannot open TUN/TAP dev /dev/net/tun: No such device (errno=19)"

[pierrepaap]

Hey everyone,
Looks like an old bug has crept back up.
Before calling it a bug i'll submit my issue here.

I'm running the container with podman on an Arch Linux system.
it worked fine until last night. When the system booted today, the container failed to restart (probably because of an automatic update)

Here is an extract of the logs:
Starting container with revision: 1103172c3288b7de681e2fb7f1378314f17f66cf
TRANSMISSION_HOME is currently set to: /config/transmission-home
Creating TUN device /dev/net/tun
Using OpenVPN provider: <redacted>
[...]
2023-07-16 17:34:45 ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such device (errno=19)
2023-07-16 17:34:45 Exiting due to fatal error

Unsurpisingly, I already have the proper arguments when calling the container:
/usr/bin/podman run \
[...]
--privileged \
[...]
-e CREATE_TUN_DEVICE=true \
[...]
-v /etc/localtime:/etc/localtime:ro docker.io/haugene/transmission-openvpn

I can check other stuff, but at this point this is what I knew to do.
Any ideas?
if it's a bug i'll register full info of course (logs, config...)

[pkishino]

Hmm, can’t find that revision.. is it latest? Try :dev or :5.0.2 tag

[pierrepaap]

yes it's supposed to be latest. I'll try 5.0.2

[pierrepaap]

tried with :dev and it worked
Starting container with revision: 42eb2ee94ef9a3ce45bdccb308f9387b36c4f6e0

then went back to latest (initially explicitly with :latest then implicitly) and it also worked
Starting container with revision: 1103172c3288b7de681e2fb7f1378314f17f66cf

So, I'm baffled and evrything is back to normal
The default UI changed though

Thanks anyways !

[pkishino]

Most have been using a very old image

…

On Mon, 17 Jul 2023 at 19:08, pierrepaap ***@***.***> wrote: tried with :dev and it worked Starting container with revision: 42eb2ee then went back to latest (initially explicitly with :latest then implicitly) and it also worked Starting container with revision: 1103172 So, I'm baffled and evrything is back to normal The default UI changed though Thanks anyways ! — Reply to this email directly, view it on GitHub <#2661 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7OFYRDVOWZXCBYDV7GFG3XQUFKJANCNFSM6AAAAAA2MBGKIA> . You are receiving this because you commented.Message ID: <haugene/docker-transmission-openvpn/repo-discussions/2661/comments/6465985 @github.com>

[pierrepaap]

Sooooo
same player plays again.
Same error again today, I tried latest, I tried dev and I tried removing the images and starting again (bothe latest and dev).
To no avail, the error has returned, to my bafflement again.

[pierrepaap]

After stopping the systemd service, rebooting and starting the systemd service manually it works again.
Something is off, i just don't know what