Error creating docker container with Active Directory support RRS feed

  • Question

  • Hi,

    I have been trying to set up a AD enabled container as per the instructions here 

    Having followed the steps through correctly, when i get round to launching the contianer with the securityopt option, i get a timeout error (failure in windows system call). Taking away the securotyopt option launches the container successfully with AD of course.

    I am using Windows 10 and wondering if there is an issue reported on this?
    Also interested to know if there are any known solutions or workarounds even

    Wednesday, October 25, 2017 3:19 PM

All replies

  • Can you enable debug logging and provide a bit more detail? (Edit C:\ProgramData\Docker\config\daemon.json and add "debug":true). A `docker version` dump would be helpful too.

    Wednesday, October 25, 2017 6:25 PM
  • Sorry am fairly new to docker windows but cant seem to see the logs in the usual appData folder on windows. Any ideas where this might be? I have enabled debug inside the dameon.json as suggested above.

    My docker version dump is 

     Version:      17.09.0-ce
     API version:  1.32
     Go version:   go1.8.3
     Git commit:   afdb6d4
     Built:        Tue Sep 26 22:40:09 2017
     OS/Arch:      windows/amd64

     Version:      17.09.0-ce
     API version:  1.32 (minimum version 1.24)
     Go version:   go1.8.3
     Git commit:   afdb6d4
     Built:        Tue Sep 26 22:50:27 2017
     OS/Arch:      windows/amd64
     Experimental: false

    • Edited by vmnadig Wednesday, November 1, 2017 3:13 PM
    Wednesday, November 1, 2017 3:12 PM
  • What Windows build are you running? Winver.exe will show this. This was broken in Windows 10 version 1703, and fixed in 1709.
    Thursday, November 16, 2017 9:04 PM
  • No it is not. I'm running Windows 10 Version 1709 (Build 16299.125) and still getting the error. More Details are also explained here: https://github.com/MicrosoftDocs/Virtualization-Documentation/issues/587
    Friday, February 23, 2018 8:02 AM
  • I'm also having this problem on 1709 16299.248. Is there a workaround?
    Sunday, February 25, 2018 6:37 PM