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

Dns settings in network stanza not usefull due incompatibility with docker task driver #8757

Closed
tantra35 opened this issue Aug 27, 2020 · 3 comments
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/networking type/bug
Milestone

Comments

@tantra35
Copy link
Contributor

tantra35 commented Aug 27, 2020

Nomad version

Nomad v0.12.3 (e6e969ad7e5c83d44758c982cfb756e081f779c3+CHANGES)

Issue

when dns settings using with bridge in in network stanza allocs can't start with docker driver

Recent Events:
Time                       Type            Description
2020-08-27T17:29:10+03:00  Killing         Sent interrupt. Waiting 1m0s before force killing
2020-08-27T17:29:10+03:00  Not Restarting  Error was unrecoverable
2020-08-27T17:29:09+03:00  Driver Failure  failed to create container: API error (400): conflicting options: dns and the network mode
2020-08-27T17:29:07+03:00  Driver          Downloading image
2020-08-27T17:29:07+03:00  Task Setup      Building Task Directory
2020-08-27T17:29:05+03:00  Received        Task received by client

Reproduction steps

Job file (if appropriate)

job "vault_debug-00"
{
        datacenters = ["test"]
        priority = 50

        update
        {
                stagger = "30m"
                max_parallel = 1
        }

        group test
        {
                count = 1

                network
                {
                        mode = "bridge"
                        dns {
                          servers = ["172.17.0.1"]
                        }
                }

                task "vault_debug_task_docker"
                {
                        driver = "docker"
                        kill_timeout = "1m"

                        config
                        {
                                image = "redis"
                        }

                        resources
                        {
                                memory = 200
                                cpu = 200
                        }
                }

                task "vault_debug_task_exec"
                {
                        driver = "exec"
                        kill_timeout = "1m"

                        config
                        {
                                command = "sleep"
                                args = ["600"]
                        }

                        resources
                        {
                                memory = 200
                                cpu = 200
                        }
                }
        }
}
@tantra35 tantra35 changed the title Dns settings in network stanza not usefull due incompatibility Dns settings in network stanza not usefull due incompatibility with docker task driver Aug 27, 2020
@shoenig shoenig added stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/networking type/bug labels Aug 27, 2020
@shoenig
Copy link
Member

shoenig commented Aug 27, 2020

Sorry about that @tantra35 ! We should already have a fix for this in #8600 going out in the next release.

@tgross
Copy link
Member

tgross commented Dec 17, 2020

This issue was closed by #8600, released in 0.12.4. (Changelog entry was missing but I've added it in #9665)

@tgross tgross closed this as completed Dec 17, 2020
@tgross tgross modified the milestones: 0.12.5, 0.12.4 Dec 17, 2020
@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 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/networking type/bug
Projects
None yet
Development

No branches or pull requests

3 participants