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

Nomad fails to run job if using network mode bridge and dns options #8431

Closed
danlsgiga opened this issue Jul 13, 2020 · 5 comments · Fixed by #8600
Closed

Nomad fails to run job if using network mode bridge and dns options #8431

danlsgiga opened this issue Jul 13, 2020 · 5 comments · Fixed by #8600

Comments

@danlsgiga
Copy link
Contributor

Nomad version

Nomad v0.12.0 (8f7fbc8)

Operating system and Environment details

CentOS Linux release 7.7.1908 (Core)

Client: Docker Engine - Community
 Version:           19.03.7
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        7141c199a2
 Built:             Wed Mar  4 01:24:10 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.12
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       48a66213fe
  Built:            Mon Jun 22 15:45:28 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Issue

Using the new dns block inside the network stanza with mode = "bridge" fails with:

failed to create container: API error (400): conflicting options: dns and the network mode
@spuder
Copy link
Contributor

spuder commented Jul 20, 2020

This is likely a duplicate of this issue. #7746

@danlsgiga
Copy link
Contributor Author

Not sure, but was this fixed on 0.12.1?

@cthayer
Copy link

cthayer commented Aug 2, 2020

@danlsgiga It doesn't seem like it's fixed in 0.12.1 as I'm currently experiencing this error in my 0.12.1 cluster.

@danlsgiga
Copy link
Contributor Author

@cthayer yup, same here!

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants