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

support distinct docker deamon configuration for windows and linux containers in dd for windows. #791

Open
jtnord opened this issue Feb 21, 2025 · 0 comments
Assignees
Labels
community_new New idea raised by a community contributor

Comments

@jtnord
Copy link

jtnord commented Feb 21, 2025

Tell us about your request
In order to avoid network conflicts with docker containers and other company internal resources you often need to configure the network range for docker containers to use to a fixed range.

e.g.

"default-addess-pools": [
    {
      "base": "[172.20.0.0/16](http://172.20.0.0/16)",
      "size": 21
    }
  ],

This works great for linux containers, but when you switch to windows containers the deamon attempts to use the same configruation file and will not start.
As the windows and linux deamons are drastically different in the network handling this is expected. Indeed it is not certain that any configuration you have should apply to both.

As such the DD app should store the configuration for the current container system, so that when on windows you are editing the config for the windows docker engine, and when on Linux you are editing the config for the Linux engine. (or the form should be extended to have 2 config fields, one for the Linux and one for the Windows engine)

Which service(s) is this request for?

Docker desktop for windows

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

WHenever I switch between windows containers and Linux containers I am either met with docker hangs as the deamon can not start, or the network does not work as I need to also manually edit the configuration which is error prone (remembering to do it is the first hurdle!), it is also combersome.

Are you currently working around the issue?

have some files on my desktop

  • for LXC when networking is broken copy some scripts to kill all containers, then copy paste the settings into docker, restart and try again...
  • for windows, this is harder as docker hanges crashes and makes it harder to edit the deamon config, but in escence try and get to the UI, paste the detailed and restart.

Additional context

Docker support case number 00136962

@jtnord jtnord added the community_new New idea raised by a community contributor label Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community_new New idea raised by a community contributor
Projects
None yet
Development

No branches or pull requests

2 participants