Azure / ACS

Azure Container Service - Bug Tracker + Announcements
65 stars 27 forks source link

ACS Kubernetes failing to pull windows container image #105

Open alexxie opened 6 years ago

alexxie commented 6 years ago

Is this a request for help?:

yes

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm) Kubernetes

What happened: Failing to pull windows container image.

What you expected to happen: Pull windows container image and start the pod

How to reproduce it (as minimally and precisely as possible):

apiVersion: apps/v1beta1 kind: Deployment metadata: name: asp-windows spec: replicas: 1 strategy: rollingUpdate: maxSurge: 1 maxUnavailable: 1 template: metadata: labels: app: app1 spec: containers:

Anything else we need to know:

Also tried pulling the same image from Docker Hub, but getting timeout error.

andyzhangx commented 6 years ago

@PatrickLang

darstahl commented 6 years ago

Looks like it might be https://github.com/moby/moby/issues/32838, for which a fix was submitted to the docker daemon in https://github.com/moby/moby/pull/35924. The issue was the some weird unicode chars were left in the layer, which was causing Golang to fail to open the file. In the linked case, it was files left in the recycle bin.

alexxie commented 6 years ago

Thanks, please keep me informed of any progress.

bublai commented 6 years ago

@alexxie, I'm new on this development & landed with same error as mentioned by you.

alexxie commented 6 years ago

@bublai Our focus is now .net core and Linux container image which seems to be more stable then the Windows container image. I have not received further update on this issue and have'nt tested it further.