Skip to content
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

Deleting unexpected lines #5131

Conversation

zedfmario
Copy link
Contributor

cc @tejal29

Fixes: #5087
Caused bY: #5088
Check this comment

Description
Due to a test in a previous PR, this file was modified with some lines included.
Those lines should not be there.

Due to a test in a previous PR, this file was modified with some lines included. Those lines should not be there.
@codecov
Copy link

codecov bot commented Dec 10, 2020

Codecov Report

Merging #5131 (ea11e1a) into master (2a8ff79) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #5131   +/-   ##
=======================================
  Coverage   72.19%   72.19%           
=======================================
  Files         381      381           
  Lines       13543    13543           
=======================================
  Hits         9777     9777           
  Misses       3050     3050           
  Partials      716      716           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2a8ff79...ea11e1a. Read the comment docs.

zedfmario referenced this pull request Dec 10, 2020
)

* enabling using another container's network stack on build process

Building docker images in a Jenkins-like environment running on a AWS EKS cluster secured with `kube2iam` requires the running pod to include an annotation. In our particular case, we share the docker daemon from the node with the running pod by mounting the socket as a volume. When `skaffold` builds a new image within this pod, it creates containers at node level due to the shared socket. Therefore, to have a brand new container handled by `kube2iam`, this container should reuse the pod's network stack –ergo the "pause" container's stack–.

Enabling the use of `container:<name|id>` network mode from `docker run` command. It allows a build process to reuse another container's stack.
> Described in [here](https://docs.docker.com/engine/reference/run/#network-settings)

* Adapting REGEXP to docker requirements

According to the `docker` CLI, when running a container with a wrong name, the following output is shown:
```
> docker run -it --name '$$' alpine
docker: Error response from daemon: Invalid container name ($$), only [a-zA-Z0-9][a-zA-Z0-9_.-] are allowed.
```
Concatenating `container:` to the expected regular expression `[a-zA-Z0-9][a-zA-Z0-9_.-]` helps us rejecting wrong values.

* runtime validation for docker network stack sharing

* overriding docker local daemon in tests

* validation with run context unified

better testing allows to unify methods

* adding skaffold error handling

* removing unnecessary dependency
Copy link
Member

@briandealwis briandealwis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops! :-)

This new functionality might make a great topic for a tutorial, if you're feeling up to it.

@briandealwis briandealwis merged commit 7a0a389 into GoogleContainerTools:master Dec 10, 2020
@zedfmario
Copy link
Contributor Author

@briandealwis, thx for merging this

Regarding the tutorial, open an issue and assign it to me. I'll gladly make it

@zedfmario zedfmario deleted the fix-getting-started-example branch November 28, 2024 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enabling using another container's network stack on build process
2 participants