Closed Kayrah87 closed 1 year ago
@Kayrah87 This action simply runs sudo openvpn --config /home/ploi/RSS_TestRunner_RSS.ovpn --daemon --log openvpn.log --writepid openvpn.pid
as this log says. Could you run this command manually inside your customized container?
Ah, I see. Yes, the openvpn.log shows the same
Tue Feb 28 15:31:13 2023 Outgoing Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key
Tue Feb 28 15:31:13 2023 Incoming Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key
Tue Feb 28 15:31:13 2023 ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2)
Tue Feb 28 15:31:13 2023 Exiting due to fatal error
Also, when I create the dev/net/tun node, I then get this error:
Tue Feb 28 15:34:03 2023 ERROR: Cannot open TUN/TAP dev /dev/net/tun: Operation not permitted (errno=1)
Tue Feb 28 15:34:03 2023 Exiting due to fatal error
Resolved. It was my bad. Had to run the container with the --privileged
flag for it to have permissions to write the tun node
Running into authorisation issues inside my test machine docker container with this:
I have tried adding in the /dev/net/tun as per google-fu, but I then get an access permissions error (errno=1)