-
Notifications
You must be signed in to change notification settings - Fork 77
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
Using networks in Dockerfile.j2 make the build failing #24
Labels
Comments
ehartmann
referenced
this issue
in ehartmann/molecule-docker
Nov 8, 2022
pbjhelmert
added a commit
to pbjhelmert/molecule-plugins
that referenced
this issue
Oct 23, 2023
Else the build will attempt to use a network that hasn't been created yet. This is essentially a resurrection of ehartmann's PR against molecule-docker before its death. Closes: ansible-community#24 Signed-off-by: Jake Helmert <jhelmert@pacificbiosciences.com>
zhan9san
pushed a commit
to pbjhelmert/molecule-plugins
that referenced
this issue
Nov 13, 2023
Else the build will attempt to use a network that hasn't been created yet. This is essentially a resurrection of ehartmann's PR against molecule-docker before its death. Closes: ansible-community#24 Signed-off-by: Jake Helmert <jhelmert@pacificbiosciences.com>
zhan9san
pushed a commit
to pbjhelmert/molecule-plugins
that referenced
this issue
Nov 13, 2023
Else the build will attempt to use a network that hasn't been created yet. This is essentially a resurrection of ehartmann's PR against molecule-docker before its death. Closes: ansible-community#24 Signed-off-by: Jake Helmert <jhelmert@pacificbiosciences.com>
pbjhelmert
added a commit
to pbjhelmert/molecule-plugins
that referenced
this issue
Nov 13, 2023
Else the build will attempt to use a network that hasn't been created yet. This is essentially a resurrection of ehartmann's PR against molecule-docker before its death. Closes: ansible-community#24 Signed-off-by: Jake Helmert <jhelmert@pacificbiosciences.com>
zhan9san
pushed a commit
that referenced
this issue
Nov 14, 2023
Else the build will attempt to use a network that hasn't been created yet. This is essentially a resurrection of ehartmann's PR against molecule-docker before its death. Closes: #24 Signed-off-by: Jake Helmert <jhelmert@pacificbiosciences.com>
Thanks a lot ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When attaching a network to an image to be built, the task
Build an Ansible compatible image (new)
is failing with this error message :The main error is :
message: network teleport-network not found
Maybe I'm misusing
docker_networks
ornetwork_mode
, so here the snippet I'm using (I'm creating 3 containers like this one) :If I understand the issue correctly, the step of creation of networks should be before the build. I've tested it locally and it works well. I'll send a PR for this issue.
Let me know if you need more information.
The text was updated successfully, but these errors were encountered: