Skip to content
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

Running sql-studio on a distroless image #33

Open
jamietanna opened this issue Jun 28, 2024 · 4 comments
Open

Running sql-studio on a distroless image #33

jamietanna opened this issue Jun 28, 2024 · 4 comments

Comments

@jamietanna
Copy link
Contributor

jamietanna commented Jun 28, 2024

This is a tracking image where I'm looking at how I'd be able to run this with as-lightweight-as-possible a Docker image.

Related: #32

Chainguard static image

FROM cgr.dev/chainguard/static:latest

COPY sql-studio /

And then when we run this image, we see:

exec /sql-studio: no such file or directory

Chainguard static glibc image

FROM cgr.dev/chainguard/static:latest-glibc

COPY sql-studio /

And then when we run this image, we see:

exec /sql-studio: no such file or directory

Google distroless static glibc image

FROM gcr.io/distroless/static-debian12:latest

COPY sql-studio /

And then when we run this image, we see:

exec /sql-studio: no such file or directory
@jamietanna
Copy link
Contributor Author

Via https://images.chainguard.dev/directory/image/static/overview we may need to tweak the build-time flags to produce a fully static image 🤔

@jamietanna
Copy link
Contributor Author

via:

% env RUSTFLAGS='-C target-feature=+crt-static' cargo build
error: cannot produce proc-macro for `async-stream-impl v0.3.5` as the target `x86_64-unknown-linux-gnu` does not support these crate types

:(

@frectonz
Copy link
Owner

frectonz commented Jul 6, 2024

Related to #31

@frectonz frectonz closed this as completed Jul 6, 2024
@jamietanna
Copy link
Contributor Author

Hey @frectonz mind closing this as Not Planned in GitHub, rather than Completed? It may indicate to others a little better that we did not resolve this, but are closing it as is

@frectonz frectonz reopened this Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants