Building multiarch docker images
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
I'm having issues building multi-arch Docker image with supercronic.
I'm able to use TARGETARCH in URL and binary name, but not in the sha1 checksum variable.
Anyone know how to deal with this?
Could we solve this with having a separate file with .sha1 extension so that you can get the checksum value from URL.
```
ENV SUPERCRONIC_URL=https://github.com/aptible/supercronic/releases/download/v0.2.29/supercronic-linux-${TARGETARCH} \
SUPERCRONIC=supercronic-linux-${TARGETARCH} \
SUPERCRONIC_SHA1SUM=${SUPERCRONIC_URL}.sha1
RUN curl -fsSLO "$SUPERCRONIC_URL" \
&& curl -fsSLO "$SUPERCRONIC_SHA1SUM" ~
&& sha1sum -c ${SUPERCRONIC}.sha1 \
&& chmod +x "$SUPERCRONIC" \
&& mv "$SUPERCRONIC" "/usr/local/bin/${SUPERCRONIC}" \
&& ln -s "/usr/local/bin/${SUPERCRONIC}" /usr/local/bin/supercronic
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the repository's multi-architecture Docker build configuration and the release checksum assets described in the issue. Verify how TARGETARCH is used for the binary and checksum, then confirm that a multi-architecture build can download the matching checksum and complete sha1 verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100