Unintentional forced sign in to Desktop?

Hi all,

Trying to configure Docker Desktop as part of a Microsoft dev box setup for some work in my org but when I try to configure it is forcing me to sign in or quit the application. My understanding is that it shouldn’t require a sign in and this is how we use it on some Macbooks.

Currently it is installed as part of a configuration yaml file using Chocolatey during the creation of the dev box, it installs Docker Desktop without error and I copy over an admin settings file. After the cleanup powershell scripts finish the dev box is rebooted and I log back in to test it. First the licence agreement appears and that can be accepted. Then the finish setting up Docker Desktop window appears to which I select ‘Use recommended settings’ and hit finish, then I get blocked.

At this point, if I do not use the admin settings json then it would prompt for admin to do the WSL install config (I install WSL on first login via powershell), saying no and continuing allows me to skip the setup and go to the dashboard without signing in.

My search so far as to the reason why I am being forced to sign in hasn’t turned up anything, beta/experimental features are off and hostnetworking being switched to disabled didn’t make a difference. Unless there is something in the admin settings I’ve misunderstood I am all out of ideas so I turn to the forums for guidance?

Any suggestions appreciated.

Admin Settings json (mostly default):

{
    "configurationFileVersion": 2,
    "exposeDockerAPIOnTCP2375": {
      "locked": true,
      "value": false
    },
    "proxy": {
      "locked": true,
      "mode": "system",
      "http": "",
      "https": "",
      "exclude": [],
      "windowsDockerdPort": 65000,
      "enableKerberosNtlm": false
    },
    "containersProxy": {
      "locked": true,
      "mode": "manual",
      "http": "",
      "https": "",
      "exclude": [],
      "pac":"",
      "transparentPorts": ""
    },
    "enhancedContainerIsolation": {
      "locked": true,
      "value": true,
      "dockerSocketMount": {
        "imageList": {
          "images": [
            "docker.io/localstack/localstack:*",
            "docker.io/testcontainers/ryuk:*"
          ]
        },
        "commandList": {
          "type": "deny",
          "commands": ["push"]
        }
      }
    },
    "linuxVM": {
      "wslEngineEnabled": {
        "locked": false,
        "value": true
      },
      "dockerDaemonOptions": {
        "locked": false,
        "value":"{\"debug\": false}"
      },
      "vpnkitCIDR": {
        "locked": false,
        "value":"192.168.65.0/24"
      }
    },
    "kubernetes": {
       "locked": false,
       "enabled": false,
       "showSystemContainers": false,
       "imagesRepository": ""
    },
    "windowsContainers": {
      "dockerDaemonOptions": {
        "locked": false,
        "value":"{\"debug\": false}"
      }
    },
    "disableUpdate": {
      "locked": false,
      "value": false
    },
    "analyticsEnabled": {
      "locked": true,
      "value": false
    },
    "extensionsEnabled": {
      "locked": true,
      "value": false
    },
    "scout": {
      "locked": false,
      "sbomIndexing": true,
      "useBackgroundIndexing": true
    },
    "allowExperimentalFeatures": {
      "locked": true,
      "value": false
    },
    "allowBetaFeatures": {
      "locked": true,
      "value": false
    },
    "blockDockerLoad": {
      "locked": true,
      "value": false
    },
    "filesharingAllowedDirectories": [
      {
        "path": "$HOME",
        "sharedByDefault": true
      },
      {
        "path":"$TMP",
        "sharedByDefault": false
      }
    ],
    "displayedOnboarding": {
      "locked": true,
      "value": false
    },
    "desktopTerminalEnabled": {
      "locked": true,
      "value": true
    }
  }

As far as I know the Enhanced container isolation is available only for Business subscribers. I never edited that file, but now I enabled the option and signed out which showed me the same window. If it didn’t require logging in before just kept it disabled, it is posisble that it changed and now you need to log in or disable that feature by default.

Apologies, complete rookie mistake.

As it turns out, WSL was not being installed via powershell as I thought. Installing WSL2 using Chocolatey during the dev box creation process solved this issue.

Thanks for the suggestions!

I don’t understand. How is signing in related to the installation of WSL2? How could you install Docker Desktop at all without the requirements? If you installed it with the HyperV backend, that should not affect any sign in window.