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
I couldn't find the answers I was looking for in the FAQ, Wiki, or Google + Reddit. I'm hoping the community can help.
The Adguard-Home snap installation instructions has a listed step to enable classic mode. Is this a hard requirement?
I'm assuming yes because the container needs to be able to bind to privileged ports?
Is there a way to run the snap container in --strict mode? I know Linux has functions to enable unprivileged processes to bind to ports <1024, but I'm not sure if that works for snap containers/processes?
If classic mode is required for this container to start (at-least for the first time), is there a way to set it to not run as root after the fact?
I could default to installing Adguard-Home natively and then utilize other methods to have it not run as root, but I was wondering if there was a way to have the best of both worlds (snap convenience + not run the container as root).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Howdy Folks,
I couldn't find the answers I was looking for in the FAQ, Wiki, or Google + Reddit. I'm hoping the community can help.
I could default to installing Adguard-Home natively and then utilize other methods to have it not run as root, but I was wondering if there was a way to have the best of both worlds (snap convenience + not run the container as root).
Beta Was this translation helpful? Give feedback.
All reactions