starred/docker-netbootxyz

Fork 0

mirror of https://github.com/netbootxyz/docker-netbootxyz.git synced 2026-04-24 22:45:49 +03:00

[GH-ISSUE #74] No new image for arm v7 since web app v0.7.0 #143

New issue

Open

opened 2026-03-01 18:33:29 +03:00 by kerem · 2 comments

kerem commented

2026-03-01 18:33:29 +03:00

Owner

Originally created by @djraw on GitHub (Oct 20, 2024).
Original GitHub issue: https://github.com/netbootxyz/docker-netbootxyz/issues/74

Hi there, I realized that the web app has been updated so I wanted to pull the latest image on my RaspberryPi.

Unfortunately I get this:

me:~ $ docker pull ghcr.io/netbootxyz/netbootxyz
Using default tag: latest
latest: Pulling from netbootxyz/netbootxyz
no matching manifest for linux/arm/v7 in the manifest list entries

Is this intended? I couldn`t find info that arm v7/armhf support has been dropped.

Well, OK, I just read closer and this is what it says on the docs page:

Supported Architectures
netboot.xyz supports x86 (both 32-bit and 64-bit) as well as arm64 architectures. Both Legacy and UEFI BIOS modes are supported. The menus identify the platform loaded and enable menu options based on the architecture loaded.

So no armhf/v7 .. But why? It worked flawless on my RasPi and still does load current menus.. until it doesn't in the future. ;)

Originally created by @djraw on GitHub (Oct 20, 2024). Original GitHub issue: https://github.com/netbootxyz/docker-netbootxyz/issues/74 Hi there, I realized that the web app has been updated so I wanted to pull the latest image on my RaspberryPi. Unfortunately I get this: ``` me:~ $ docker pull ghcr.io/netbootxyz/netbootxyz Using default tag: latest latest: Pulling from netbootxyz/netbootxyz no matching manifest for linux/arm/v7 in the manifest list entries ``` Is this intended? I couldn`t find info that arm v7/armhf support has been dropped. Well, OK, I just read closer and this is what it says on the docs page: > Supported Architectures > netboot.xyz supports x86 (both 32-bit and 64-bit) as well as arm64 architectures. Both Legacy and UEFI BIOS modes are supported. The menus identify the platform loaded and enable menu options based on the architecture loaded. So no armhf/v7 .. But why? It worked flawless on my RasPi and still does load current menus.. until it doesn't in the future. ;)

kerem commented

2026-03-01 18:33:30 +03:00

Author

Owner

@antonym commented on GitHub (Oct 23, 2024):

I think I originally dropped it because the Github Actions build job would get stuck on building the arm/v7 image. I'm trying it again on Alpine 3.20.3 but it still appears to be hanging the build job.

@antonym commented on GitHub (Oct 23, 2024): I think I originally dropped it because the Github Actions build job would get stuck on building the arm/v7 image. I'm trying it again on Alpine 3.20.3 but it still appears to be hanging the build job.

kerem commented

2026-03-01 18:33:30 +03:00

Author

Owner

@antonym commented on GitHub (Oct 23, 2024):

I might have to play around with some hacks to get it working:

https://github.com/docker/build-push-action/issues/1071

@antonym commented on GitHub (Oct 23, 2024): I might have to play around with some hacks to get it working: https://github.com/docker/build-push-action/issues/1071

No labels

enhancement

pull-request

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/docker-netbootxyz#143

No description provided.

Rows
Columns