-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Cannot open TUN/TAP dev /dev/net/tun: No such file or directory #39
Comments
Not sure what the problem is. Seems like an issue with your kernel or hosting provider. Can you share these details? |
VM is from Hetzner: https://www.hetzner.de/en/hosting/produkte_vserver/vx6 Kernel is standard CoreOS: CoreOS stable (607.0.0) Actually might have to do a rethink on how I do this. Now I understand things better - I was hopping to be able to update the routes on the host server, something that may not actually be possible from within a docker container... |
Same problem for me.
Everything went fine until the start of the container, i the have :
A quick google seem to indicate that the problem is about the --privileged flag, but i've run my container as stated within the docs with --cap-add=NET_ADMIN
|
Seems strange. Works fine for me on a fresh DO droplet running Ubuntu
Kernel version via
|
The https://github.com/kylemanna/docker-openvpn/blob/master/bin/ovpn_run#L16 |
Thanks. Think I must have missed this. Don't know how @SR-G was starting openvpn, however looks like I was doing it wrong... Unfortunately, I am not in a position to test this any longer. |
Thanks for the update. Closing unless someone can reproduce. |
hi, FYI, I just experienced the same problem:
on a Raspberry Pi 1 Host with Hypriot 0.6:
I figured that it works with the
so maybe this helps someone out there, for me it works fine now. :-) UPDATE: as I'm just going through the scripts here in more detail I have to add that I did not use the scripts here, so I did not run the UPDATE 2: of course now that I created the /dev/net/tun device as in your script, it works as expected! so please rather ignore this comment :-) |
@blacky14 Thanks for the hint wrt |
I am seeing this problem with CentOS Atomic. Specifically, either of these: Results in this: The only thing that doesn't is this: Installation particulars: The ISO I started with came from here: http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host-7-Installer.iso |
In my case the issue was that CentOS Atomic uses SELinux by default. I had to do the following prior to following the README instructions:
This is clearly stated in the docs but I had only read the quick start. Might be worth mentioning in the main README at the top of Quick Start that some precursor steps need to be taken if you're using SELinux. |
@vchav73 thanks for the update and glad to hear you got it working! |
mkdir -p /dev/net |
Hello,
Did I do something wrong?
As far as I can tell this should work:
Maybe the fact this is Core OS is significant, can't see why though - Core OS itself has tun support:
Also:
Hmmm. ----privileged works fine, but the documentation says that is only required for Docker < 1.2 - wonder if some other --cap-add= option is required for 1.5???
Thanks
The text was updated successfully, but these errors were encountered: