-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Allow dependent image pull from insecure registry #562
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
Conversation
|
+1 |
1 similar comment
|
+1 |
|
I'm waiting for this as well |
|
@tjrivera Thanks for the contribution! Would really like to get this in Fig 1.0.1. Any chance we could get a test with a mocked client? |
|
As I understand it, this adds |
|
@aanand it already is |
|
👍 |
|
@aanand is that an LGTM? |
|
Yes, LGTM, though I wouldn't mind a test either. |
PR #490 Provides the ability to pull from an insecure registry by passing --allow-insecure-ssl. This commit extends the work done in #490 and adds the ability to pass --allow-insecure-ssl to the up and run commands which will attempt to pull dependent images if they do not exist. Signed-off-by: Tyler Rivera <riverat2@email.chop.edu>
|
LGTM |
1 similar comment
|
LGTM |
Allow dependent image pull from insecure registry
|
Great stuff. Thanks @tjrivera! |
Allow dependent image pull from insecure registry Signed-off-by: Yuval Kohavi <yuval.kohavi@gmail.com>
PR #490 Provides the ability to pull from an insecure registry by passing --allow-insecure-ssl. This commit extends the work done in #490 and adds the ability to pass --allow-insecure-ssl to the
upandruncommands which will attempt to pull dependent images if they do not exist.Signed-off-by: Tyler Rivera riverat2@email.chop.edu