AdguardTeam/AdGuardHome

Wrong OS/ARCH for Docker Image

Open

#1265 opened on Dec 17, 2019

View on GitHub
 (10 comments) (1 reaction) (0 assignees)Go (34,000 stars) (2,333 forks)batch import
P2: Highbughelp wanted

Description

For the Docker Images on hub.docker.com the wrong OS/ARCH is shown:

For example for the image tagged with arm64-latest the OS/ARCH is linux/amd64. The correct OS/ARCH should be linux/arm/v6

Because of this issue the container could not be deployed via docker swarm on a raspberry node. The swarm manager does not deploy it because of the incorrect CPU Architecture.

Contributor guide

Tech stack
dockergo
Domain
devopsinfrastructure
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Docker basicsmulti architecture images
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Examine the Dockerfile and build scripts in the repository to understand how images are built and tagged. Use `docker manifest inspect` on the current images to verify the incorrect architecture. Then update the build process to correctly set the architecture label, likely in the Dockerfile or CI configuration. Check comments in issue #1265 for any suggested fixes or discussion.