mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-08 21:59:09 -05:00
[GH-ISSUE #1871] Running via rootless Podman not working #10795
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Zogalicious on GitHub (Nov 16, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1871
Describe the Bug
The installer script did not work for me. I fixed those errors, but I still can't access the Web UI.
Environment
To Reproduce
First, I got the error
Command 'podman network exists pangolin' returned non-zero exit status 1.I fixed this by: (1) Selecting
notoWould you like to install and start the containers?(2) Setting the owner of all the files and folders, that the installer created, to my user account withsudo chown -R $(id -u):$(id -g) <pangolin_install_path>. (3) Creating thedbdirectory withmkdir <pangolin_install_path>/db, which was not created by runningpodman-compose up.When I run
podman-compose up, I get:I tried to access
localhost:3002via SSH TCP forwarding withssh -L 8080:localhost:3002 <user>@<ip>. However, when I navigate tolocalhost:8080in my browser, the page does not load, and I seechannel 3: open failed: connect failed: Connection refusedin the Podman logs on the server. I also tried with ports 3000 and 3001, and same thing. I get this error message with any port I try forwarding to my local machine.The latest Guix package of
podman-composeis version 1.2.0. I installed version 1.5.0 bypipto check if this made a difference. The logs above are whenpodman-compose upis run with version 1.5.0.When run with version 1.2.0, I get:
I tried accessing the HTTP server in my browser on port 3004, but this was not reachable.
I have all the recommended ports (80, 443, 51820, 21820) open in the firewall.
Expected Behavior
No errors, and ability to access the Web UI.
@github-actions[bot] commented on GitHub (Dec 1, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Dec 16, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.