Release docker images on ghcr registry #1678

Closed
opened 2026-02-28 02:29:10 -05:00 by deekerman · 4 comments
Owner

Originally created by @ksurl on GitHub (Dec 24, 2022).

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

Consider release of the docker images on the github container registry as an alternative/backup to docker hub due to free/anonymous account pull limits

✔️ Solution

tag new builds with ghcr.io/louislam/uptime-kuma in addition to the existing implicit docker.io tag and push to ghcr.

Alternatives

No response

📝 Additional Context

No response

Originally created by @ksurl on GitHub (Dec 24, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description Consider release of the docker images on the github container registry as an alternative/backup to docker hub due to free/anonymous account pull limits ### ✔️ Solution tag new builds with ghcr.io/louislam/uptime-kuma in addition to the existing implicit docker.io tag and push to ghcr. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_
deekerman 2026-02-28 02:29:10 -05:00
Author
Owner

@pascaliske commented on GitHub (Mar 10, 2023):

This is an easy feature! Also would be awesome if builds / pushes could be automated using GitHub Actions or some other CI provider...

@pascaliske commented on GitHub (Mar 10, 2023): This is an easy feature! Also would be awesome if builds / pushes could be automated using GitHub Actions or some other CI provider...
Author
Owner

@ksurl commented on GitHub (Jun 18, 2023):

Is this planned for future releases or can this issue be closed?

@ksurl commented on GitHub (Jun 18, 2023): Is this planned for future releases or can this issue be closed?
Author
Owner

@CommanderStorm commented on GitHub (Jun 18, 2023):

This issue is a duplicate of #53.
Please refrain from posting duplicates, as this just makes issue managemnt harder.

See https://github.com/louislam/uptime-kuma/pull/213.
Louis is not keen on this

⇒ Given that he is the BDFL and the only maintainer (see https://github.com/louislam/uptime-kuma/pull/1349, this is by coice), this likely won't happen.

@CommanderStorm commented on GitHub (Jun 18, 2023): This issue is a duplicate of #53. Please refrain from posting duplicates, as this just makes issue managemnt harder. See https://github.com/louislam/uptime-kuma/pull/213. Louis is not keen on this ⇒ Given that he is the BDFL and the only maintainer (see https://github.com/louislam/uptime-kuma/pull/1349, this is by coice), this likely won't happen.
Author
Owner

@ksurl commented on GitHub (Jun 18, 2023):

Fair enough but it was not marked as dupe 6 months ago. I'll go ahead and close this.

@ksurl commented on GitHub (Jun 18, 2023): Fair enough but it was not marked as dupe 6 months ago. I'll go ahead and close this.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#1678
No description provided.