http - How does docker manage to get a return code of 200 instead of 401 -



http - How does docker manage to get a return code of 200 instead of 401 -

at work docker not able pull images:

[b209d3c5] +job pull(ubuntu, ) [debug] registry.go:372 [registry] calling https://index.docker.io/v1/repositories/ubuntu/images [debug] http.go:160 https://index.docker.io/v1/repositories/ubuntu/images -- headers: map[user-agent:[docker/1.0.0 go/go1.2.2 git-commit/63fe64c kernel/3.15.1-1-arch os/linux arch/amd64]] [debug] server.go:1182 retrieving tag list [debug] http.go:160 https://cdn-registry-1.docker.io/v1/repositories/library/ubuntu/tags -- headers: map[user-agent:[docker/1.0.0 go/go1.2.2 git-commit/63fe64c kernel/3.15.1-1-arch os/linux arch/amd64]] [debug] registry.go:327 got status code 401 https://cdn-registry-1.docker.io/v1/repositories/library/ubuntu/tags [error] server.go:1185 not reach registry endpoint not reach registry endpoint [b209d3c5] -job pull(ubuntu, ) = err (1)

if manually seek access sec url reliably results in 401, too.

however @ home same command somehow manages retrieve tags:

[4e9acee4] +job pull(ubuntu, ) [debug] registry.go:372 [registry] calling https://index.docker.io/v1/repositories/ubuntu/images [debug] http.go:160 https://index.docker.io/v1/repositories/ubuntu/images -- headers: map[user-agent:[docker/1.0.0 go/go1.2.2 git-commit/63fe64c kernel/3.14.6-1-arch os/linux arch/amd64]] [debug] server.go:1182 retrieving tag list [debug] http.go:160 https://cdn-registry-1.docker.io/v1/repositories/library/ubuntu/tags -- headers: map[user-agent:[docker/1.0.0 go/go1.2.2 git-commit/63fe64c kernel/3.14.6-1-arch os/linux arch/amd64]] [debug] registry.go:327 got status code 200 https://cdn-registry-1.docker.io/v1/repositories/library/ubuntu/tags [debug] server.go:1197 registering tags [...]

the question is: how did docker instance manage 200 result?

is there way inspect communication? (wireshark not https encrypted.)

probably way reading source code. don't know much go language.

can think of improve solution that, building docker on own , adding debugging prints?

seems rest phone call requires valid authorization: token ... header. seems company proxy breaks header. :(

building docker source painless.

http go docker

Comments

Popular posts from this blog

php - Android app custom user registration and login with cookie using facebook sdk -

django - Access session in user model .save() -

php - .htaccess Multiple Rewrite Rules / Prioritizing -