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.

Sign up for GitHub

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

Jump to bottom

Fix: Snap build #6

Open
leon3s opened this issue Feb 2, 2024 · 2 comments
Open

Fix: Snap build #6

leon3s opened this issue Feb 2, 2024 · 2 comments
Labels
help wanted Extra attention is needed

Comments

@leon3s
Copy link
Owner

leon3s commented Feb 2, 2024

Seems like on snap we need to create a netplan to make network change on the host,
This should be more investigated.
@leon3s leon3s mentioned this issue Mar 25, 2024
Closed
@leon3s leon3s added help wanted Extra attention is needed good first issue Good for newcomers labels Mar 25, 2024
@leon3s
Copy link
Owner Author

leon3s commented Jul 15, 2024

See https://forum.snapcraft.io/t/request-classic-confinement-for-wireguard-gui/41038

@leon3s leon3s changed the title Snap: Create a netplan for the associated profile Fix: Snap build Aug 9, 2024
@leon3s leon3s removed the good first issue Good for newcomers label Aug 9, 2024
@leon3s
Copy link
Owner Author

leon3s commented Aug 9, 2024

To avoid using sudo when starting the application, we can considere linking the c library of wireguard to use native call from the rust code instead of using the generated shell script.
Then pass a env variable to know when we are running inside a snap or natively

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@leon3s