hedefalk
commented
1 year ago Now I've gone through an initContainer and copied over only this single file in rw mode and i can both edit the file and create other files as root in the container:
root@transmission-transmission-openvpn-6ddd5d88b-vxlbf:/etc/openvpn/custom# echo "#" > default.ovpn
root@transmission-transmission-openvpn-6ddd5d88b-vxlbf:/etc/openvpn/custom# tail default.ovpn
#
root@transmission-transmission-openvpn-6ddd5d88b-vxlbf:/etc/openvpn/custom# echo foo > bar
root@transmission-transmission-openvpn-6ddd5d88b-vxlbf:/etc/openvpn/custom# ls -l
total 13
-rw-r--r-- 1 root root 4 Mar 16 19:02 bar
-rw-r--r-- 1 root root 360 Nov 16 21:08 config-failure.sh
-rwxr-xr-x 1 root root 5059 Mar 16 19:00 default.ovpnbut the sed script still fails with "Device or resource busy":
Defaulted container "transmission-openvpn" out of: transmission-openvpn, copy-config (init)
Starting container with revision: b33d0fe4c938259a0d4eb844e55468f387456121
Creating TUN device /dev/net/tun
Using OpenVPN provider: CUSTOM
Modifying /etc/openvpn/custom/default.ovpn for best behaviour in this container
Modification: Point auth-user-pass option to the username/password file
Modification: Change ca certificate path
sed: cannot rename /etc/openvpn/custom/sedder7I7: Device or resource busy
sed: cannot rename /etc/openvpn/custom/sedroPZvZ: Device or resource busy
Modification: Change ping options
sed: cannot rename /etc/openvpn/custom/sedf46Cyq: Device or resource busy
sed: cannot rename /etc/openvpn/custom/sedZ55wGr: Device or resource busy
sed: cannot rename /etc/openvpn/custom/sedKGdT1H: Device or resource busy
sed: cannot rename /etc/openvpn/custom/sed5Qtw2k: Device or resource busy
Modification: Update/set resolv-retry to 15 seconds
sed: cannot rename /etc/openvpn/custom/sedDtSyF0: Device or resource busy
sed: cannot rename /etc/openvpn/custom/sedfvpNtD: Device or resource busy
Modification: Change tls-crypt keyfile path
sed: cannot rename /etc/openvpn/custom/sedg9piAL: Device or resource busy
Modification: Set output verbosity to 3
sed: cannot rename /etc/openvpn/custom/sedeWKJGp: Device or resource busy
sed: cannot rename /etc/openvpn/custom/sedICjECq: Device or resource busy
Modification: Remap SIGUSR1 signal to SIGTERM, avoid OpenVPN restart loop
sed: cannot rename /etc/openvpn/custom/sed4rnHXB: Device or resource busy
sed: cannot rename /etc/openvpn/custom/sedZDovPN: Device or resource busy
Modification: Updating status for config failure detection
sed: cannot rename /etc/openvpn/custom/sedeSfbU3: Device or resource busy
sed: cannot rename /etc/openvpn/custom/sed6SmIli: Device or resource busy
Setting OpenVPN credentials...
adding route to local network 192.168.0.0/24 via 10.42.0.1 dev eth0
2023-03-16 18:58:59 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2023-03-16 18:58:59 OpenVPN 2.5.5 aarch64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 14 2022
2023-03-16 18:58:59 library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10
2023-03-16 18:58:59 neither stdin nor stderr are a tty device and you have neither a controlling tty nor systemd - can't ask for 'Enter Auth Username:'. If you used --daemon, you need to use --askpass to make passphrase-protected keys work, and you can not use --auth-nocache.
2023-03-16 18:58:59 Exiting due to fatal error
pkishino
Is there a pinned issue for this?
Is there an existing or similar issue/discussion for this?
Is there any comment in the documentation for this?
Is this related to a provider?
Are you using the latest release?
Have you tried using the dev branch latest?
Docker run config used
I'm using a k8s with a pretty bare bones helm chart and this is my values.yaml which would be very similar to the docker run command. I'm trying protonvpn but got auth issues using the out-of-the-box configuration. So I've downloaded their latest ovpn files and mounted by configmap into the container:
Current Behavior
Startup fails when trying to do edits in
/etc/openvpn/custom/default.ovpnwhich I cannot seem to mount writable.If I look in the container, the file is mounted just fine:
the only thing I cannot do is edit the mounted file:
which seems to align with the errors in the log. But wasn't that supposed to be ok, to mount an external read-only config?
Expected Behavior
I didn't expect the need to edit the config file in place accoring to the example here:
https://haugene.github.io/docker-transmission-openvpn/supported-providers/#if_you_only_need_to_mount_one_file
How have you tried to solve the problem?
1) I've tried coming up with a solution using initContainers to copy from a mounted read-only ConfigMap onto another volume that could then be mounted in the container, but it doesn't seem like it will work with the existing container folder structure of a
/etc/openvpn/customalready containing a file (config-failure.sh) and then I need to add another file (default.ovpn) that is writable.Log output
HW/SW Environment
Anything else?
No response