Bug: ERROR creating tun device: unix opening TUN device file: operation not permitted

[sammyt107]

Is this urgent?

Yes

Host OS

Debian OMV

CPU arch

x86_64

VPN service provider

Private Internet Access

What are you using to run the container

Portainer

What is the version of Gluetun

latest built on 2024-12-14 21:09:55

What's the problem 🤔

I'm getting this creating tun error on portainer, tried using latest and v3 versions but doesn't work on either.

Share your logs (at least 10 lines)

2024-12-22T20:28:21Z ERROR creating tun device: unix opening TUN device file: operation not permitted

Share your configuration

No response

[github-actions]

@qdm12 is more or less the only maintainer of this project and works on it in his free time.
Please:

• do not ask for updates, be patient
• 👍 the issue to show your support instead of commenting
  @qdm12 usually checks issues at least once a week, if this is a new urgent bug,
  revert to an older tagged container image

[GentleHoneyLover]

I have the same error since the last container image update...

I had to add this to my compose as a workaround. Not sure why it needs it (previously it worked without it and the tunnel is created inside the container anyway). With this device mapped, gluten is running normally again...

devices:
      - /dev/net/tun:/dev/net/tun

@qdm12 can you please advise on why gluten seems to want the tun device mapping from the host? Has anything changed recently (in the image or in the docker engine itself)?

[sammyt107]

@GentleHoneyLover Thanks for the help and that seems to have worked, will leave open for now to see if we get a response on the tun device mapping

[danthonywalker]

I am getting the same issue. I haven't changed versions, all I have done recently is restart my system and suddenly this issue is appearing. The workaround from @GentleHoneyLover works, but I'm wondering what has changed.

[raph521]

containerd.io was likely updated on your system.

There's another issue about it with more details:
#2606

[qdm12]

Duplicated of now resolved #2606

About to cut a release which will log out a fix when encountering this error.

[github-actions]

Closed issues are NOT monitored, so commenting here is likely to be not seen.
If you think this is still unresolved and have more information to bring, please create another issue.

This is an automated comment setup because @qdm12 is the sole maintainer of this project
which became too popular to monitor issues closed.