-
Notifications
You must be signed in to change notification settings - Fork 332
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
[FEATURE] Podman support #584
Comments
My attempts to run the bw-docker-proxy container and scheduler under podman were not successful. I started the socket with this command (rootless):
The socket now exists under /run/user/1001/podman/podman.sock. Afterwards I created the containers as described in the documentation:
No I get the following errors in the bw-scheduler container:
The bw-docker-proxy output looks like this:
Need assistance. A solution without using the docker compatibility socket would be fine as well. |
Hi,
since the 1.5.0 release Bunkerweb is no longer working on Podman, because the new scheduler container needs docker API access. Of course you can enable the Docker compatibility socket of Podman but I'm looking for a solutions without the socket.
Is it possible to run Bunkerweb on Podman without the compatibility socket?
The text was updated successfully, but these errors were encountered: