-
Notifications
You must be signed in to change notification settings - Fork 92
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
data_image http/https proxy #147
Labels
Comments
I also have to work in an airgapped environment without internet. We do have an Artifactory Server which has access to the internet and thus can proxy Docker and other repos.
Where exactly does your kitchen run fail? Without logs it is hard to guess what the problem is. |
jbartko
pushed a commit
to jbartko/kitchen-dokken
that referenced
this issue
Aug 31, 2018
I believe this addresses test-kitchen#147
jbartko
pushed a commit
to jbartko/kitchen-dokken
that referenced
this issue
Aug 31, 2018
Addresses test-kitchen#147 **User Story** As a build engineer, I want to use kitchen-dokken behind a proxy without direct access to the internet, So that it may be used in corporate CI/CD pipelines. **Test Case** *GIVEN* instance executing kitchen does not have direct internet access *WHEN* performing integration testing with kitchen-dokken *EXPECT* the ability to pull Docker images via proxy *EXPECT* the ability to control proxy access while building the baked-in data_image Maybe not the best approach, but it provides the minimum flexibility needed to perform testing in an environment with strict access control.
jbartko
pushed a commit
to jbartko/kitchen-dokken
that referenced
this issue
Aug 31, 2018
Addresses test-kitchen#147 **User Story** As a build engineer, I want to use kitchen-dokken behind a proxy without direct access to the internet, So that it may be used in corporate CI/CD pipelines. **Test Case** *GIVEN* instance executing kitchen does not have direct internet access *WHEN* performing integration testing with kitchen-dokken *EXPECT* the ability to pull Docker images via proxy *EXPECT* the ability to control proxy access while building the baked-in data_image Maybe not the best approach, but it provides the minimum flexibility needed to perform testing in an environment with strict access control.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My CI jobs live behind a proxy and it seems like there is no way to interject intermediate steps or docker build-arg for the data_image.
https://github.com/someara/kitchen-dokken/blob/master/lib/kitchen/helpers.rb
This is an issue as I cannot install RPMs without the proxy properly being setup.
Am I missing something or someway to work around this? Maybe even being able to provide your own image here?
The text was updated successfully, but these errors were encountered: