How can we improve the Azure Kubernetes Service (AKS)?

Increase Kubernetes node docker version to 17.05.x & +

In order to take full advantage of running a VSTS agent in AKS, the docker version of the node must be at least 17.05 & + to support building project using multi-stage DockerFile.

127 votes
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)

We’ll send you updates on this idea

Mathieu Nadeau shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

10 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • Roman commented  ·   ·  Flag as inappropriate

    Newer Docker is 100% needed.

    Many pod creations on a heavily loaded cluster are just failing.

    pod-s90pk 0/1 ContainerCannotRun 0 5m

    The logs are full of:

    Warning Failed 5m kubelet, k8s-default-41404144-8 Error: failed to start container "nginx-refresh": Error response from daemon: {"message":"oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:258: applying cgroup configuration for process caused \\\"failed to write 24809 to cgroup.procs: write /sys/fs/cgroup/cpu,cpuacct/docker/nginx-refresh/cgroup.procs: invalid argument\\\"\"\n"}

  • Dave Thompson commented  ·   ·  Flag as inappropriate

    We believe that we may be being hit by bugs in the current Docker version deployed on AKS. This is anecdotal to a degree due to the version of Docker being so out of date and memory of past bugs fading. Specifically we suspect that chown and chmod steps in Dockerfiles aren't always resulting in permission changes being made consistently/deterministically across large numbers of files in a Linux container. We're seeing this cause problems in PHP containers that are spun up (fixed on pod deletion+recreation). Would REALLY like AKS to pick up a newer Docker version for two reasons:
    1) VSTS / Azure DevOps build agent use to build multi-stage dockerfiles - we're super excited about the potential there
    2) Pick up bugfixes in Docker such as for the suspected issue mentioned above.

Feedback and Knowledge Base