-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Use podman #16
Use podman #16
Conversation
This is currently waiting on #12 which the original owner of the SourceBans container should be reviewing my PR later this week |
A downside is |
- -cpus | ||
- "1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
make this use cpuset
Currently containers do not start unless the service is manually started, but I think this is a bug and I've reported it at containers/podman#24468 |
Still blocked, seems like the Quadlet issue exists even on modern builds of Podman. I'll come back to this some other time, I've already spent a few hours trying to find a workaround without basically rewriting everything. |
blocked by several issues that aren't really solveable without root user intervention and compiling binaries outside of a distribution's package manager (except for maybe Fedora). closing |
Closes #1.
This is a pretty big change, but the benefits on the security side are noticeable. The
docker
role is synonymous withwheel
on a lot of servers, so consolidating this to be guaranteed userland-only removes the need for giving the user additional access at all.