After installing the latest version (hide.me-linux-amd64-0.9.9.tar.gz ) of the Hide.me CLI VPN client on Manjaro Linux, the systemd service for the VPN connection fails to start due to a missing /run/systemd/resolve directory, which results in a Failed to set up mount namespacing error.
Steps to Reproduce
Install Hide.me CLI VPN client version 0.9.9 on Manjaro Linux.
Enable and start the systemd service for a VPN connection.
Observe the service failing to start with a status=226/NAMESPACE error.
Workaround Implemented
I modified "/opt/hide.me/hide.me@.service" by removing the reference to /run/systemd/resolve in the ReadWritePaths directive. This allowed the service to start successfully.
Suggested Fix
It might be beneficial to evaluate the necessity of referencing /run/systemd/resolve in the service file, considering it may not exist on all systems or when systemd-resolved is not in use. An alternative approach or configuration flexibility would help accommodate various system setups.
Additional Context
This problem seems to have been addressed in a previous commit (3795591), but the issue persists or has resurfaced under certain conditions.
Description
After installing the latest version (hide.me-linux-amd64-0.9.9.tar.gz ) of the Hide.me CLI VPN client on Manjaro Linux, the systemd service for the VPN connection fails to start due to a missing
/run/systemd/resolve
directory, which results in aFailed to set up mount namespacing
error.Steps to Reproduce
status=226/NAMESPACE
error.Workaround Implemented
I modified "/opt/hide.me/hide.me@.service" by removing the reference to
/run/systemd/resolve
in theReadWritePaths
directive. This allowed the service to start successfully.Suggested Fix
It might be beneficial to evaluate the necessity of referencing
/run/systemd/resolve
in the service file, considering it may not exist on all systems or whensystemd-resolved
is not in use. An alternative approach or configuration flexibility would help accommodate various system setups.Additional Context
This problem seems to have been addressed in a previous commit (3795591), but the issue persists or has resurfaced under certain conditions.
Thank you for looking into this matter. Thomas