starred/panel
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-02-19 11:20:28 +03:00
Code Issues 42 Packages Projects Releases 11 Wiki Activity

Missing linux/amd64 OS for docker main image #253

New Issue
Closed
opened 2026-02-04 17:17:01 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 17:17:01 +03:00
Owner
Copy Link

Originally created by @SirEndii on GitHub (Feb 9, 2025).

Current Behavior

I tried to test a canary feature. But when I tried to use the main tag it failed to fetch the image since there is now proper image for linux/amd64

Expected Behavior

Provide a linux/amd64 os image for the main tag like we have it for wings

Steps to Reproduce

Look at https://github.com/pelican-dev/panel/pkgs/container/panel

Panel Version

canary

Wings Version

1.0.0-beta9

Games and/or Eggs Affected

No response

Docker Image

No response

Error Logs

Is there an existing issue for this?

  • I have searched the existing issues before opening this issue.
  • I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
  • I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
Originally created by @SirEndii on GitHub (Feb 9, 2025). ### Current Behavior I tried to test a canary feature. But when I tried to use the `main` tag it failed to fetch the image since there is now proper image for linux/amd64 ### Expected Behavior Provide a linux/amd64 os image for the main tag like we have it for wings ### Steps to Reproduce Look at https://github.com/pelican-dev/panel/pkgs/container/panel ### Panel Version canary ### Wings Version 1.0.0-beta9 ### Games and/or Eggs Affected _No response_ ### Docker Image _No response_ ### Error Logs ```bash ``` ### Is there an existing issue for this? - [x] I have searched the existing issues before opening this issue. - [x] I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server. - [x] I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
OVERLORD commented 2026-02-04 17:17:15 +03:00
Author
Owner
Copy Link

@parkervcp commented on GitHub (Feb 9, 2025):

The default image is latest not main and so far as I know we are not building a canary image.

@parkervcp commented on GitHub (Feb 9, 2025): The default image is `latest` not `main` and so far as I know we are not building a canary image.
OVERLORD commented 2026-02-04 17:17:22 +03:00
Author
Owner
Copy Link

@SirEndii commented on GitHub (Feb 9, 2025):

There is a canary image
https://github.com/pelican-dev/panel/pkgs/container/panel/352016785?tag=main

But not built with linux/amd64 arch

@SirEndii commented on GitHub (Feb 9, 2025): There is a canary image https://github.com/pelican-dev/panel/pkgs/container/panel/352016785?tag=main But not built with linux/amd64 arch
OVERLORD commented 2026-02-04 17:17:25 +03:00
Author
Owner
Copy Link

@rmartinoscar commented on GitHub (Feb 9, 2025):

Hey thanks for your report @QuintenQVD0 is investigating
The most probable cause is https://github.com/pelican-dev/panel/pull/920

@rmartinoscar commented on GitHub (Feb 9, 2025): Hey thanks for your report @QuintenQVD0 is investigating The most probable cause is https://github.com/pelican-dev/panel/pull/920
OVERLORD commented 2026-02-04 17:17:32 +03:00
Author
Owner
Copy Link

@QuintenQVD0 commented on GitHub (Feb 9, 2025):

I have looked into this for the past 2 hours and what I have done:

  • bypass the docker_meta step
  • Disabling labels
  • in the matrix, specify the platform directly
  • try to rollback docker/build-push-action to v5
  • bump the labs syntax version
  • remove the labs syntax
  • run without cache
  • in setup-buildx-action force the target with the platforms argument
  • try to use the Ubuntu 22.04 runner

All of it did not fix it, the workflow that pushed last is the only one that can be pulled or will show up.
The workflows build and push for the right arch and all the buildx arguments seem fine to me so I have no idea how I can fix this

/usr/bin/docker buildx build --build-arg VERSION=dev-b6528c7 --cache-from type=gha,scope=ubuntu-24.04     --cache-to type=gha,scope=ubuntu-24.04,mode=max     --file ./Dockerfile --iidfile /home/runner/work/_temp/docker-actions-toolkit-JaA4vI/build-iidfile-9dfb377423.txt --platform linux/amd64 --attest type=provenance,mode=max,builder-id=https://github.com/QuintenQVD0/panel/actions/runs/13227991779/attempts/1 --tag ghcr.io/quintenqvd0/panel:main --metadata-file /home/runner/work/_temp/docker-actions-toolkit-JaA4vI/build-metadata-5f11a7e53d.json --push .

/usr/bin/docker buildx build --build-arg VERSION=dev-b6528c7 --cache-from type=gha,scope=ubuntu-24.04-arm --cache-to type=gha,scope=ubuntu-24.04-arm,mode=max --file ./Dockerfile --iidfile /home/runner/work/_temp/docker-actions-toolkit-KiFyWh/build-iidfile-c4762d97b9.txt --platform linux/arm64 --attest type=provenance,mode=max,builder-id=https://github.com/QuintenQVD0/panel/actions/runs/13227991779/attempts/1 --tag ghcr.io/quintenqvd0/panel:main --metadata-file /home/runner/work/_temp/docker-actions-toolkit-KiFyWh/build-metadata-e55499db64.json --push .
@QuintenQVD0 commented on GitHub (Feb 9, 2025): I have looked into this for the past 2 hours and what I have done: - bypass the docker_meta step - Disabling labels - in the matrix, specify the platform directly - try to rollback docker/build-push-action to v5 - bump the labs syntax version - remove the labs syntax - run without cache - in setup-buildx-action force the target with the platforms argument - try to use the Ubuntu 22.04 runner All of it did not fix it, the workflow that pushed last is the only one that can be pulled or will show up. The workflows build and push for the right arch and all the buildx arguments seem fine to me so I have no idea how I can fix this ```sh /usr/bin/docker buildx build --build-arg VERSION=dev-b6528c7 --cache-from type=gha,scope=ubuntu-24.04 --cache-to type=gha,scope=ubuntu-24.04,mode=max --file ./Dockerfile --iidfile /home/runner/work/_temp/docker-actions-toolkit-JaA4vI/build-iidfile-9dfb377423.txt --platform linux/amd64 --attest type=provenance,mode=max,builder-id=https://github.com/QuintenQVD0/panel/actions/runs/13227991779/attempts/1 --tag ghcr.io/quintenqvd0/panel:main --metadata-file /home/runner/work/_temp/docker-actions-toolkit-JaA4vI/build-metadata-5f11a7e53d.json --push . /usr/bin/docker buildx build --build-arg VERSION=dev-b6528c7 --cache-from type=gha,scope=ubuntu-24.04-arm --cache-to type=gha,scope=ubuntu-24.04-arm,mode=max --file ./Dockerfile --iidfile /home/runner/work/_temp/docker-actions-toolkit-KiFyWh/build-iidfile-c4762d97b9.txt --platform linux/arm64 --attest type=provenance,mode=max,builder-id=https://github.com/QuintenQVD0/panel/actions/runs/13227991779/attempts/1 --tag ghcr.io/quintenqvd0/panel:main --metadata-file /home/runner/work/_temp/docker-actions-toolkit-KiFyWh/build-metadata-e55499db64.json --push . ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel#253
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?