Conversation
There was a problem hiding this comment.
Pull request overview
This PR addresses an ARM64 startup failure for the plexio service by avoiding an amd64-only prebuilt image pull and aiming to force a local build instead.
Changes:
- Updated the
plexioservice image reference from a GHCR image to a local image name to avoid platform mismatch pulls. - Minor formatting/normalization in the profiles list section (no functional change).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| services: | ||
| plexio: | ||
| image: ghcr.io/vanchaxy/plexio | ||
| image: plexio |
There was a problem hiding this comment.
Using image: plexio still leaves Compose free to pull an external image named plexio (e.g., from Docker Hub) depending on the command/pull policy, which can reintroduce the same class of startup failures and/or run an unintended image. To guarantee ARM64 hosts always use the local build, either remove the image: field entirely (let Compose name the built image) or keep it but set an explicit pull_policy: never (and/or use a clearly local-only name).
| image: plexio | |
| image: plexio | |
| pull_policy: never |
Problem
The plexio service fails to start on ARM64 hosts (e.g., Oracle Cloud ARM VPS) with the following error:
This is because
image: ghcr.io/vanchaxy/plexiocauses Docker Compose to attempt pulling the pre-built image from GHCR, which is only published forlinux/amd64. Even though abuild:block is defined, the registry image reference takes priority and triggers the platform mismatch.Fix
image: ghcr.io/vanchaxy/plexiotoimage: plexioso Docker Compose uses the local build instead of trying to pull the amd64-only registry image.