Skip to content
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

[FEAT] Don't start container if there is an error in config #278

Closed
1 task done
kuznetsss opened this issue Jun 27, 2023 · 3 comments
Closed
1 task done

[FEAT] Don't start container if there is an error in config #278

kuznetsss opened this issue Jun 27, 2023 · 3 comments

Comments

@kuznetsss
Copy link

Is this a new feature request?

  • I have searched the existing issues

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:

Or add a new service to start after wireguard which will check whether wireguard network interface has been created.

@kuznetsss kuznetsss added the enhancement New feature or request label Jun 27, 2023
@github-actions
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@github-actions
Copy link

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.

@LinuxServer-CI LinuxServer-CI closed this as not planned Won't fix, can't repro, duplicate, stale Sep 27, 2023
@github-actions
Copy link

This issue is locked due to inactivity

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

2 participants