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

[Bug]: Simd docker image is missing basic binaires to use the docker #15672

Closed
webmaster128 opened this issue Apr 3, 2023 · 0 comments · Fixed by #15703
Closed

[Bug]: Simd docker image is missing basic binaires to use the docker #15672

webmaster128 opened this issue Apr 3, 2023 · 0 comments · Fixed by #15703
Assignees
Labels

Comments

@webmaster128
Copy link
Member

webmaster128 commented Apr 3, 2023

Summary of Bug

Since 0.47, the interchainio/simapp image misses the ost fundamental tools to operate in this docker image, such as

  • sh
  • echo
  • file
  • ls

This makes it hard to debug #15670 and makes it impossible to use the docker image for CosmJS testing.

I guess the reason is the change from alpine:edge to gcr.io/distroless/base in #14793.

In order to restore the previous functionality, I suggest using alpine:latest (latest stable) for the runtime image instead.

Version

SDK 0.47
Docker: interchainio/simapp:v0.47.1 and ghcr.io/cosmos/simapp:latest

Steps to Reproduce

Open a shell

$ docker run --rm -it interchainio/simapp:v0.47.1 sh
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown.

Get simd file

$ docker run --rm interchainio/simapp:v0.47.1 file /usr/bin/simd
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "file": executable file not found in $PATH: unknown.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants