-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
change argoexec
to use alpine
rather that debian
#5720
Labels
Milestone
Comments
Using alpine fixes all the problems. |
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Apr 20, 2021
Signed-off-by: Alex Collins <[email protected]>
alexec
added a commit
that referenced
this issue
May 25, 2021
Signed-off-by: Alex Collins <[email protected]>
alexec
added a commit
that referenced
this issue
Jun 5, 2021
jfarrell
added a commit
to jfarrell/argo-workflows
that referenced
this issue
Feb 28, 2022
Reverts back to previous argoexec baseimage of debian due to ARG_MAX limit differences in debian versus alpine causing a regression in behavior. reverts: PR argoproj#5720
jfarrell
added a commit
to jfarrell/argo-workflows
that referenced
this issue
Feb 28, 2022
Reverts back to previous argoexec baseimage of debian due to ARG_MAX limit differences in debian versus alpine causing a regression in behavior. reverts: PR argoproj#5720 resolves: issues argoproj#7586
jfarrell
added a commit
to jfarrell/argo-workflows
that referenced
this issue
Mar 2, 2022
Reverts back to previous argoexec baseimage of debian due to ARG_MAX limit differences in debian versus alpine causing a regression in behavior. reverts: PR argoproj#5720 resolves: issues argoproj#7586
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Debian base image (10) has not been updated since 2019 and has 14 high severity vulnerabilities that are only fixed in 11 which will not be released for some months.
Using Alpine we can:
The text was updated successfully, but these errors were encountered: