-
Notifications
You must be signed in to change notification settings - Fork 15
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
Support rootless containers #151
Comments
Can you not map port 80 to something else? Example: ports:
- 5000:80 Or are you using host networking? |
I have such mapping. Error is thrown by NV_INIT
|
Okay, so, I spent a bit of time on this. I think this may not be related to port 80, but rather a different problem. I was able to run a rootless container on my computer as-is with no issue, admittedly with Docker instead of Podman. The error you're getting is related to how internally the container attempts to automate the webtrees setup wizard. It starts up Apache on port 80, sends a HTTP request, and then reconfigures Apache to however you selected. It's erroring on this request though. If port 80 was blocked, I would expect the Apache server to never start.
|
Thank you for your help.
I removed WT_ ENV vars and now getting groupadd errors I tried using all combinations of UserNS and/or User+Group and/or PGUID+PUID
or
I am using quadlets. Here is my
|
Thanks for the info, unfortunately I have not yet had time to work on this more. |
I think supporting rootless containers is going to be a larger effort than an easy change. I'm adding this to my infinite backlog. Unfortunately no idea when I will get to it. I was trying to copy some of the Linuxserver images, but I'll need to do more research. |
Any possibility to use ENV to set HTTP/HTTPS ports?
I run rootless container using podman,, this means port < 1024 can not be opened (by default).
Sure, I can enable it but it would be good to add to ENV vars
WT_HTTP_PORT
WT_HTTPS_PORT
Here is traceback
The text was updated successfully, but these errors were encountered: