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

crane: Gitlab runner issue because of new busybox image #1640

Closed
antonvdl opened this issue Apr 8, 2023 · 1 comment
Closed

crane: Gitlab runner issue because of new busybox image #1640

antonvdl opened this issue Apr 8, 2023 · 1 comment
Labels
bug Something isn't working lifecycle/stale

Comments

@antonvdl
Copy link

antonvdl commented Apr 8, 2023

Describe the bug

Since #1638 there is an issue with gitlab runners.
Gitlab runner uses BashDetectShellScript see bash.go for the script.

This script detects a /bin/bash file in the Chainguard image, but the /bin/bash is not working
/bin/bash is a symlink to /bin/busybox; which automatically runs /bin/busybox bash.
Running /bin/bash or /bin/busybox bash will result in an error.

To Reproduce

/bin $ /bin/bash
bash: applet not found

/bin $ /bin/busybox bash
bash: applet not found

Expected behavior

/bin $ /bin/bash
sh: /bin/bash: not found

@antonvdl antonvdl added the bug Something isn't working label Apr 8, 2023
@github-actions
Copy link

github-actions bot commented Jul 8, 2023

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Keep fresh with the 'lifecycle/frozen' label.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working lifecycle/stale
Projects
None yet
Development

No branches or pull requests

1 participant