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

executor:debug doesn't expose /bin/sh #1828

Closed
rvillane opened this issue Nov 25, 2021 · 3 comments
Closed

executor:debug doesn't expose /bin/sh #1828

rvillane opened this issue Nov 25, 2021 · 3 comments
Labels
area/container For all bugs related to the kaniko container kind/bug Something isn't working priority/p2 High impact feature/bug. Will get a lot of users happy

Comments

@rvillane
Copy link

Actual behavior
executor:debug image doesn't expose /bin/sh but executor:v1.7.0-debug does and they are supposed to be the same image per v1.7.0 release notes.

Ticket #1748 added a symlink to /bin/sh and the actual change is reflected here.

Expected behavior
executor:debug image should expose /bin/sh.

To Reproduce
Steps to reproduce the behavior:

  1. Run this command: docker run -it --entrypoint=/bin/sh gcr.io/kaniko-project/executor:debug, it will produce the following error:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown.
  1. Now run this command: docker run -it --entrypoint=/bin/sh gcr.io/kaniko-project/executor:v1.7.0-debug, it works fine:
/workspace # ls -ls /bin/sh
     0 lrwxrwxrwx    1 0        0               11 Oct 20 02:35 /bin/sh -> /busybox/sh

Triage Notes for the Maintainers

Description Yes/No
Please check if this a new feature you are proposing
  • No
Please check if the build works in docker but not in kaniko
  • No
Please check if this error is seen when you use --cache flag
  • No
Please check if your dockerfile is a multistage dockerfile
  • No

I suspect gcr.io/kaniko-project/executor image tags are assigned incorrectly.

@dallmair
Copy link

dallmair commented Feb 3, 2022

At the moment, debug is the same as v1.6.0-debug as per @imjasonh 1.7.0 has a few regressions (#1788 (comment)).

@imjasonh
Copy link
Collaborator

imjasonh commented Feb 3, 2022

It's true. Please try the latest commit-tagged image to see if this is resolved at head.

gcr.io/kaniko-project/executor:d0fe83024cac52fdcf77ea6e634cefd90abc7f6e-debug

@aaron-prindle
Copy link
Collaborator

Going to close this this seems to have been resolved in future kaniko releases. As of today (6/13/23), the latest release of kaniko v1.11.0 has debug and v1.11.1-debug tags pointing to the correct image:
image

@aaron-prindle aaron-prindle added area/container For all bugs related to the kaniko container kind/bug Something isn't working priority/p2 High impact feature/bug. Will get a lot of users happy labels Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/container For all bugs related to the kaniko container kind/bug Something isn't working priority/p2 High impact feature/bug. Will get a lot of users happy
Projects
None yet
Development

No branches or pull requests

4 participants