Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
sammyt107 opened this issue Dec 22, 2024 · 5 comments

Comments

@sammyt107
Copy link

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

Copy link
Contributor

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

@GentleHoneyLover
Copy link

GentleHoneyLover commented Dec 23, 2024

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
Copy link
Author

@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
Copy link

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
Copy link

raph521 commented Dec 24, 2024

containerd.io was likely updated on your system.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants