You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Is this a new feature request?
Wanted change
Fail to start container if there is no config file or if there are errors in the config
Reason for change
I think it would be better to explicitly fail to start container if wireguard interface was not created
Proposed code change
Maybe add a check of return code of
wg-quick
command here:docker-wireguard/root/etc/s6-overlay/s6-rc.d/svc-wireguard/run
Line 4 in fbb3a4b
Or add a new service to start after wireguard which will check whether wireguard network interface has been created.
The text was updated successfully, but these errors were encountered: