moby: BUG: docker-compose running on Windows doesn't pull images from private Registry

Output of docker version:

Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      linux/amd64

Output of docker info:

Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 1.12.0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 0
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.15-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.95 GiB
Name: moby
ID: 3NYZ:RZBK:ZVUJ:GAHH:4TXY:U7CS:5V3O:L5VG:5K67:RUNK:PECQ:SGLP
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
 127.0.0.0/8

Additional environment details (AWS, VirtualBox, physical, etc.):

OS: Windows 10 Pro Two private registry tested

Steps to reproduce the issue:

1.docker login private.registry.tld(Should result: Login Successful)

C:\Users\user\test_project>docker login  private.registry.tld
Username (chucknorris):
Password:
Login Succeeded

2.docker-compose up -d

C:\Users\user\test_project>docker-compose up -d
Pulling npm-test (private.registry.tld/npm-boiler:latest)...
ERROR: Get https://private.registry.tld/v2/npm-boiler/manifests/latest: unauthorized: authentication required

3.Using docker-compose pull


ERROR: Get https://private.registry.tld/v2/npm-boiler/manifests/latest: unauthorized: authentication required

4.If I pull them one by one works

C:\Users\user\test_project>docker pull private.registry.tld/npm-boiler
Using default tag: latest
latest: Pulling from npm-boiler
8ad8b3f87b37: Downloading [======>                                            ] 6.291 MB/51.37 MB
751fe39c4d34: Downloading [======================>                            ] 8.257 MB/18.53 MB

5.insecure-registry already used, doesn’t works.

What should I do? Can I use docker-compose inside Windows? Private-Registry Problems?

I will appreciate your help, thank you!

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 16 (8 by maintainers)

Most upvoted comments

I don’t quite understand why you’re getting that error, but I think the first problem is that you’re running this against a Linux Docker daemon. You need to run a Windows Docker daemon to pull and run Windows Docker images. I posted an overview here: https://forums.docker.com/t/linux-and-windows-images-side-by-side/20518/4

If you fix that, I think you’ll find that docker-compose won’t work on Windows. This is because Compose relies on overlay networking support that’s not yet ready on Windows.

This is probably as far as you’ll get:

version: '2'
services:
  test:
    image: friism/foo-vote:win
    networks:
      - nat
networks:
  nat:
    external: true

docker-compose up
Pulling test (friism/foo-vote:win)...
win: Pulling from friism/foo-vote
Digest: sha256:877371808abe9ab20a494dc653da64583efc3e81244fc695d86ff5685e130688
Status: Downloaded newer image for friism/foo-vote:win
Creating composeprivaterepo_test_1

ERROR: for test  Windows does not support disconnecting a running container from a network
ERROR: Encountered errors while bringing up the project.

friism on Aug 31, 2016