none
Getting error on pulling images in Windows Container RRS feed

  • Question

  • Getting error "The parameter is incorrect" on pulling image off docker hub. Docker info is below. Tried to remove/add Hyper-V,containers and docker to no avail.

    Containers: 0
     Running: 0
     Paused: 0
     Stopped: 0
    Images: 0
    Server Version: 17.03.1-ce
    Storage Driver: windowsfilter
     Windows:
    Logging Driver: json-file
    Plugins:
     Volume: local
     Network: l2bridge l2tunnel nat null overlay transparent
    Swarm: inactive
    Default Isolation: hyperv
    Kernel Version: 10.0 15063 (15063.0.amd64fre.rs2_release.170317-1834)
    Operating System: Windows 10 Enterprise
    OSType: windows
    Architecture: x86_64
    CPUs: 8
    Total Memory: 63.92 GiB
    Name: CND70637PKZBook
    ID: BHAJ:4OFC:RVPW:3EPD:BF5V:BTT6:XKKS:MLS6:3VAE:65QQ:K2PW:P5OY
    Docker Root Dir: D:\images
    Debug Mode (client): false
    Debug Mode (server): true
     File Descriptors: -1
     Goroutines: 18
     System Time: 2017-05-12T16:37:23.9112935-05:00
     EventsListeners: 0
    Registry: https://index.docker.io/v1/
    Experimental: true
    Insecure Registries:
     127.0.0.0/8
    Live Restore Enabled: false

     

    PS C:\Users\gsuvalia> docker pull microsoft/nanoserver
    Using default tag: latest
    latest: Pulling from microsoft/nanoserver
    bce2fbc256ea: Extracting [==================================================>] 252.7 MB/252.7 MB
    4a8c367fd46d: Download complete
    failed to register layer: re-exec error: exit status 1: output: ProcessBaseLayer D:\images\windowsfilter\749d2e58b44079db30ca8aadf815c4443edc0aeb3f78411db5cbee7b7b3b8c92: The parameter is incorrect.

    Friday, May 12, 2017 9:38 PM

Answers

  • All images. After several days of troubleshooting I found out that docker somehow thought that I had BitLocker encrypted drive which I did not. I had to enable BitLocker manually on drive to make it work. Disabling BitLocker later still allowed this to functino.
    Monday, May 15, 2017 5:43 PM

All replies

  • Is it the same behavior for other images?  Or just the nanoserver image?

    Is it only for hyper-v containers or also standard runtime?

    Monday, May 15, 2017 5:41 PM
  • All images. After several days of troubleshooting I found out that docker somehow thought that I had BitLocker encrypted drive which I did not. I had to enable BitLocker manually on drive to make it work. Disabling BitLocker later still allowed this to functino.
    Monday, May 15, 2017 5:43 PM
  • So you couldn't pull images because Docker thought the drive was encrypted?

    Or you couldn't pull images because Docker thought you did not have Bitlocker enabled?

    Or something else entirely?

    Monday, May 15, 2017 6:34 PM
  • What I said was a speculation on my part. All I know is that while drive was NOT encrypted docker would fail to pull images. As soon as I encrypted drive pull started working. Decrypting drive later on still allowed for docker pull to work. All I can assume docker though for some reason that drive was encrypted and was trying to decrypt plain data and was failing or something.
    Monday, May 15, 2017 6:37 PM
  • Fair enough.  Thanks for following up!  Glad things are working again :)

    Let us know if you need anything

    Tuesday, May 16, 2017 8:27 PM