-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spire 1.6.4 and 1.7.0 releases for Linux/arm64 fail down with sqlite3 settings in config #4346
Labels
priority/urgent
Issue is approved and is must be completed in the assigned milestone
Milestone
Comments
The steps for reproducing in MacOS:
|
bellycat77
changed the title
Spire 1.6.4 and 1.7.0 releases for Linux/arm64 fails down with sqlite3 settings in config
Spire 1.6.4 and 1.7.0 releases for Linux/arm64 fail down with sqlite3 settings in config
Jul 19, 2023
evan2645
added
triage/in-progress
Issue triage is in progress
priority/urgent
Issue is approved and is must be completed in the assigned milestone
and removed
triage/in-progress
Issue triage is in progress
labels
Jul 20, 2023
It looks like release 1.7.2 didn't solve the issue
|
azdagron
added a commit
to azdagron/spire
that referenced
this issue
Sep 13, 2023
This gives us static binaries linked against musl for our release artifacts, unifying our libc dependency for both docker and non-docker and simplifying our build tooling. Since artifact building is now fairly complicated and really only part of the CI/CD pipeline, got rid of the Makefile target for it. Fixes: spiffe#4346 Signed-off-by: Andrew Harding <[email protected]>
azdagron
added a commit
to azdagron/spire
that referenced
this issue
Sep 13, 2023
This gives us static binaries linked against musl for our release artifacts, unifying our libc dependency for both docker and non-docker and simplifying our build tooling. Since artifact building is now fairly complicated and really only part of the CI/CD pipeline, got rid of the Makefile target for it. Fixes: spiffe#4346 Signed-off-by: Andrew Harding <[email protected]>
azdagron
added a commit
to azdagron/spire
that referenced
this issue
Sep 13, 2023
This gives us static binaries linked against musl for our release artifacts, unifying our libc dependency for both docker and non-docker and simplifying our build tooling. Since artifact building is now fairly complicated and really only part of the CI/CD pipeline, got rid of the Makefile target for it. Fixes: spiffe#4346 Signed-off-by: Andrew Harding <[email protected]>
azdagron
added a commit
to azdagron/spire
that referenced
this issue
Sep 13, 2023
This gives us static binaries linked against musl for our release artifacts, unifying our libc dependency for both docker and non-docker and simplifying our build tooling. Since artifact building is now fairly complicated and really only part of the CI/CD pipeline, got rid of the Makefile target for it. Fixes: spiffe#4346 Signed-off-by: Andrew Harding <[email protected]>
rturner3
pushed a commit
that referenced
this issue
Sep 13, 2023
* Source binaries for linux artifacts from docker images This gives us static binaries linked against musl for our release artifacts, unifying our libc dependency for both docker and non-docker and simplifying our build tooling. Since artifact building is now fairly complicated and really only part of the CI/CD pipeline, got rid of the Makefile target for it. Fixes: #4346 Signed-off-by: Andrew Harding <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Spire server got from release archives https://github.com/spiffe/spire/releases/download/v1.7.0/spire-1.7.0-linux-arm64-glibc.tar.gz and https://github.com/spiffe/spire/releases/download/v1.6.4/spire-1.6.4-linux-arm64-glibc.tar.gz fails down when ran in VM with error like:
Environment details
OS: macOS Ventura 13.4/ CPU M1
Docker Desktop: v4.21.1
Docker Engine: 24.0.2
Used docker images: golang:1.20.5-buster and arm64v8/ubuntu:22.04
N.B.: The server built inside the container from sources works well
The text was updated successfully, but these errors were encountered: