github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-06 08:56:45 -05:00
Code Issues 464 Packages Projects Releases 71 Wiki Activity

[GH-ISSUE #1296] Quick Install: Podman installation fails due to unsupported networking option (--network service:gerbil) #3785

New Issue
Closed
opened 2026-04-20 07:54:39 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-20 07:54:39 -05:00
Owner
Copy Link

Originally created by @arousalspoon204 on GitHub (Aug 17, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1296

Description:

When installing Pangolin with Podman instead of Docker, the installer fails to start the traefik container.

Steps to reproduce: installer.log

Run the installer on a Debian VPS.

Choose podman when asked whether to use Docker or Podman.

Proceed with the installation using default values.

Observe the container startup phase.

Observed behavior:

The installer attempts to run traefik with the following option:

--network service:gerbil

Podman does not recognize this option and exits with:

Error: invalid option for network service: unknown bridge network option: gerbil
exit code: 125

As a result, the traefik container is not created, and subsequent podman start traefik fails with:

Error: no container with name or ID "traefik" found: no such container

Additional issues noticed during installation:

The installer tries to stop/remove containers (traefik, gerbil, pangolin) before creating them, which results in repeated errors such as:

Error: no container with name or ID "traefik" found: no such container
exit code: 125

Despite failures, the installer still reports Installation complete!, which can be misleading.

Environment:

Debian 12 VPS (Hetzner)

Podman version 4.3.1

Pangolin installer (latest as of August 2025)

Summary:

The installer is not fully compatible with Podman due to unsupported Docker-specific networking syntax and error handling issues during container lifecycle management.

Originally created by @arousalspoon204 on GitHub (Aug 17, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1296 ### Description: When installing Pangolin with **Podman** instead of Docker, the installer fails to start the traefik container. ### Steps to reproduce: [installer.log](https://github.com/user-attachments/files/21823486/installer.log) Run the installer on a Debian VPS. Choose podman when asked whether to use Docker or Podman. Proceed with the installation using default values. Observe the container startup phase. ### Observed behavior: The installer attempts to run traefik with the following option: `--network service:gerbil` Podman does not recognize this option and exits with: ``` Error: invalid option for network service: unknown bridge network option: gerbil exit code: 125 ``` As a result, the traefik container is not created, and subsequent podman start traefik fails with: `Error: no container with name or ID "traefik" found: no such container` ### Additional issues noticed during installation: The installer tries to stop/remove containers (traefik, gerbil, pangolin) before creating them, which results in repeated errors such as: ``` Error: no container with name or ID "traefik" found: no such container exit code: 125 ``` Despite failures, the installer still reports Installation complete!, which can be misleading. ### Environment: Debian 12 VPS (Hetzner) Podman version 4.3.1 Pangolin installer (latest as of August 2025) ### Summary: The installer is not fully compatible with Podman due to unsupported Docker-specific networking syntax and error handling issues during container lifecycle management.
GiteaMirror commented 2026-04-20 07:54:41 -05:00
Author
Owner
Copy Link

@placobravo commented on GitHub (Aug 21, 2025):

With podman version 5.4.0 everything is fine since the "--network service:gerbil" is correctly interpreted. I just tried it on RockyLinux 10.0.

To be fair I think the issue is not even with podman itself, but rather with podman-compose. I do not know exactly in which version of podman-compose the "service" option was introduced , but in the current version it works fine

<!-- gh-comment-id:3211688671 --> @placobravo commented on GitHub (Aug 21, 2025): With podman version 5.4.0 everything is fine since the "_--network service:gerbil_" is correctly interpreted. I just tried it on RockyLinux 10.0. To be fair I think the issue is not even with podman itself, but rather with podman-compose. I do not know exactly in which version of podman-compose the "service" option was introduced , but in the current version it works fine
GiteaMirror commented 2026-04-20 07:54:43 -05:00
Author
Owner
Copy Link

@arousalspoon204 commented on GitHub (Aug 22, 2025):

You're right, everything works fine under RockyLinux. The problem is Debian with outdated tool versions.

Thank you very much for your help.

<!-- gh-comment-id:3214140355 --> @arousalspoon204 commented on GitHub (Aug 22, 2025): You're right, everything works fine under RockyLinux. The problem is Debian with outdated tool versions. Thank you very much for your help.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#3785
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?