mirror of
https://github.com/SAP/jenkins-library.git
synced 2025-01-18 05:18:24 +02:00
--ignore-path=/ in order to fix (#3570)
``` ERROR: Process exited immediately after creation. See output below Executing /busybox/sh script inside container container-exec of pod dynamic-agent-... ``` On jenkins Co-authored-by: Robert Ozga <robert.ozga@sap.com> Co-authored-by: Christian Volk <christian.volk@sap.com>
This commit is contained in:
parent
a1988f6808
commit
9fa8390ef2
@ -178,7 +178,7 @@ You can activate multiple builds using the parameters
|
||||
}
|
||||
|
||||
func addKanikoExecuteFlags(cmd *cobra.Command, stepConfig *kanikoExecuteOptions) {
|
||||
cmd.Flags().StringSliceVar(&stepConfig.BuildOptions, "buildOptions", []string{`--skip-tls-verify-pull`, `--ignore-path`, `/busybox`}, "Defines a list of build options for the [kaniko](https://github.com/GoogleContainerTools/kaniko) build.")
|
||||
cmd.Flags().StringSliceVar(&stepConfig.BuildOptions, "buildOptions", []string{`--skip-tls-verify-pull`, `--ignore-path=/`}, "Defines a list of build options for the [kaniko](https://github.com/GoogleContainerTools/kaniko) build.")
|
||||
cmd.Flags().StringVar(&stepConfig.BuildSettingsInfo, "buildSettingsInfo", os.Getenv("PIPER_buildSettingsInfo"), "Build settings info is typically filled by the step automatically to create information about the build settings that were used during the mta build. This information is typically used for compliance related processes.")
|
||||
cmd.Flags().BoolVar(&stepConfig.ContainerMultiImageBuild, "containerMultiImageBuild", false, "Defines if multiple containers should be build. Dockerfiles are used using the pattern **/Dockerfile*. Excludes can be defined via [`containerMultiImageBuildExcludes`](#containermultiimagebuildexscludes).")
|
||||
cmd.Flags().StringSliceVar(&stepConfig.ContainerMultiImageBuildExcludes, "containerMultiImageBuildExcludes", []string{}, "Defines a list of Dockerfile paths to exclude from the build when using [`containerMultiImageBuild`](#containermultiimagebuild).")
|
||||
@ -216,7 +216,7 @@ func kanikoExecuteMetadata() config.StepData {
|
||||
Type: "[]string",
|
||||
Mandatory: false,
|
||||
Aliases: []config.Alias{},
|
||||
Default: []string{`--skip-tls-verify-pull`, `--ignore-path`, `/busybox`},
|
||||
Default: []string{`--skip-tls-verify-pull`, `--ignore-path=/`},
|
||||
},
|
||||
{
|
||||
Name: "buildSettingsInfo",
|
||||
|
@ -34,10 +34,9 @@ spec:
|
||||
- STEPS
|
||||
default:
|
||||
- --skip-tls-verify-pull
|
||||
# fixing Kaniko issue https://github.com/GoogleContainerTools/kaniko/issues/1586
|
||||
# as per comment https://github.com/GoogleContainerTools/kaniko/issues/1586#issuecomment-945718536
|
||||
- --ignore-path
|
||||
- /busybox
|
||||
# fixing Kaniko issue with multistage builds and missing busybox
|
||||
# suggestion from https://github.com/GoogleContainerTools/kaniko/issues/1586#issuecomment-945718536 did not solve the problem
|
||||
- --ignore-path=/
|
||||
- name: buildSettingsInfo
|
||||
type: string
|
||||
description: Build settings info is typically filled by the step automatically to create information about the build settings that were used during the mta build. This information is typically used for compliance related processes.
|
||||
|
Loading…
x
Reference in New Issue
Block a user