You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When porter builds a bundle, we lookup the repository digest of any referenced images. Previously we did that with Pull, which always allowed connections to insecure registries. Now that we are executing a HEAD request instead to get the digest, instead of pulling the image with PullImage, we can be more explicit like we are with the publish commnad.
I have added --insecure-registry to porter build, so that the bundle author can decide when building if they want to allow connections to an insecure registry (http or self-signed certificates).
Signed-off-by: Carolyn Van Slyck <[email protected]>
Copy file name to clipboardExpand all lines: cmd/porter/bundle.go
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -91,6 +91,8 @@ The docker driver builds the bundle image using the local Docker host. To use a
91
91
"Do not use the Docker cache when building the bundle's invocation image.")
92
92
f.StringArrayVar(&opts.Customs, "custom", nil,
93
93
"Define an individual key-value pair for the custom section in the form of NAME=VALUE. Use dot notation to specify a nested custom field. May be specified multiple times. Max length is 5,000 characters when used as a build argument.")
0 commit comments