github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-06 20:59:07 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[PR #1040] [CLOSED] Add podman support to the installer #7219

New Issue
Closed
opened 2026-04-25 16:07:51 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-25 16:07:51 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/fosrl/pangolin/pull/1040
Author: @wayneyaoo
Created: 7/9/2025
Status: ❌ Closed

Base: main ← Head: main

📄 Description

Community Contribution License Agreement

By creating this pull request, I grant the project maintainers an unlimited,
perpetual license to use, modify, and redistribute these contributions under any terms they
choose, including both the AGPLv3 and the Fossorial Commercial license terms. I
represent that I have the right to grant this license for all contributed content.

Description

The change primarily adds support for podman installation within the installer. The installer will prompt for selection between docker (the default) and podman.

A few points to notice:

  1. If podman and podman-compose are not available, the installer will exit. This is by design at the moment because installing for people like what the installer does to docker is involving. If this is needed, I can do that in later iterations.
  2. I added docker.io to the compose template file. This is because for freshly installed podman, it needs to add an entry to the registeries.conf so that image short name resolves. But I don't think editing this on behalf of people makes a lot of sense, so I resort to use explicit full name in the image entry. This has benefit to docker too because explicitness is still better than being implicit.
  3. I added a few targets to the Makefile without breaking existing ones in CI. This is easier for local dev.

How to test?

Spin up a Debian/Ubtuntu machine and manually install podman and podman-compose, then run the installer.

For some reason, Debian 12 default podman and podman-compose's versions are too old and they have problem processing the docker-compose.yml. We should specify to use newer versions (>= v5.5.2 of podman, >= 1.4.1 podman-compose). Otherwise it'll appear as pangolin installation being broken which is not the case.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/fosrl/pangolin/pull/1040 **Author:** [@wayneyaoo](https://github.com/wayneyaoo) **Created:** 7/9/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📄 Description ## Community Contribution License Agreement By creating this pull request, I grant the project maintainers an unlimited, perpetual license to use, modify, and redistribute these contributions under any terms they choose, including both the AGPLv3 and the Fossorial Commercial license terms. I represent that I have the right to grant this license for all contributed content. ## Description The change primarily adds support for podman installation within the installer. The installer will prompt for selection between docker (the default) and podman. A few points to notice: 1. If podman and podman-compose are not available, the installer will exit. This is by design at the moment because installing for people like what the installer does to docker is involving. If this is needed, I can do that in later iterations. 2. I added `docker.io` to the compose template file. This is because for freshly installed podman, it needs to add an entry to the `registeries.conf` so that image short name resolves. But I don't think editing this on behalf of people makes a lot of sense, so I resort to use explicit full name in the image entry. This has benefit to docker too because explicitness is still better than being implicit. 3. I added a few targets to the Makefile without breaking existing ones in CI. This is easier for local dev. ## How to test? Spin up a Debian/Ubtuntu machine and manually install podman and podman-compose, then run the installer. For some reason, Debian 12 default podman and podman-compose's versions are too old and they have problem processing the `docker-compose.yml`. We should specify to use newer versions (>= v5.5.2 of podman, >= 1.4.1 podman-compose). Otherwise it'll appear as pangolin installation being broken which is not the case. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-25 16:07:51 -05:00
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 pull-request
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#7219
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?