install on arm64
G3z opened this issue · 2 comments
G3z commented
Hello,
I'm trying do build multiarch docker images but i think no arm64 package is available for alpine:
apk add --repository https://alpine.secrethub.io/alpine/edge/main --allow-untrusted secrethub-cli
#8 0.388 fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/main/aarch64/APKINDEX.tar.gz
#8 1.257 fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/community/aarch64/APKINDEX.tar.gz
#8 2.455 v3.13.6-28-g0fb6231dad [https://dl-cdn.alpinelinux.org/alpine/v3.13/main]
#8 2.455 v3.13.6-29-g6b33ef5588 [https://dl-cdn.alpinelinux.org/alpine/v3.13/community]
#8 2.455 OK: 13736 distinct packages available
#8 4.042 OK: 5 MiB in 14 packages
#8 4.218 fetch https://alpine.secrethub.io/alpine/edge/main/aarch64/APKINDEX.tar.gz
#8 4.602 ERROR: https://alpine.secrethub.io/alpine/edge/main: No such file or directory
#8 4.603 WARNING: Ignoring https://alpine.secrethub.io/alpine/edge/main: No such file or directory
#8 6.077 ERROR: unable to select packages:
#8 6.243 secrethub-cli (no such package):
#8 6.243 required by: world[secrethub-cli]
this works fine for amd64
G3z commented
this is my workaround for now
FROM alpine:3.14
ARG TARGETPLATFORM
ARG BUILDPLATFORM
RUN apk update && apk upgrade && apk add --no-cache curl
RUN mkdir -p /usr/local/secrethub
RUN URL=$(curl -L -s https://api.github.com/repos/secrethub/secrethub-cli/releases/latest | grep -o -E "https://(.*)secrethub-(.*)-${TARGETPLATFORM/\//-}.tar.gz") && \
curl -L -s $URL | tar -xzC /usr/local/secrethub && \
ln -s /usr/local/secrethub/bin/secrethub /usr/local/bin/secrethub
SimonBarendse commented
Hi @G3z, thank you for reporting this request!
We're currently focused on getting SecretHub functionality ported to 1Password so that you and others can migrate to using 1Password and get all the benefits of both solutions. We are not adding new features to SecretHub. We'll definitely take this request into account for installation of the 1Password CLI.
Given that there is a workaround available, would it be reasonable for you to continue to use this workaround until you're ready to migrate to 1Password?