I am currently using priviliedged build and mounting dockersock volume on kubernetes. Is this going to break when I upgrade to kube 1.19?

Drone Support
1

I have heard the kube 1.19 drops support for docker. I’m not sure what effect that will have on my builds and I am scared to update my cluster in case everything breaks.

I am using privileged build with the following script to build docker containers, does anyone know if I’ll be broken and what the solution would be to move forward if so?

steps:

  • name: Build Application Image
    image: operations/awscli:8
    pull: if-not-exists
    privileged: true
    environment:
    APP_NAME:
    from_secret: APP_NAME
    ECR_ENDPOINT:
    from_secret: ECR_ENDPOINT
    AWS_ACCESS_KEY_ID:
    from_secret: AWS_ACCESS_KEY_ID
    AWS_SECRET_ACCESS_KEY:
    from_secret: AWS_SECRET_ACCESS_KEY
    NPM_AUTH_TOKEN:
    from_secret: NPM_AUTH_TOKEN
    DOCKERHUB_TOKEN:
    from_secret: DOCKERHUB_TOKEN
    volumes:
    • name: dockersock
      path: /var/run
      commands:
    • eval $(aws ecr get-login --region ca-central-1 --no-include-email)
    • timeout 15s sh -c – ‘while (! docker info > /dev/null 2>&1); do :; done;’ || true
    • set +o pipefail
    • docker pull $ECR_ENDPOINT/cache-registry:$APP_NAME-output || true
    • docker login --username operations --password $DOCKERHUB_TOKEN
    • docker build --build-arg npm_auth_token=$NPM_AUTH_TOKEN -t $APP_NAME
      –cache-from $ECR_ENDPOINT/cache-registry:$APP_NAME-output
      –tag $ECR_ENDPOINT/$APP_NAME:${DRONE_COMMIT}
      –tag $ECR_ENDPOINT/$APP_NAME:latest
      –tag $ECR_ENDPOINT/cache-registry:$APP_NAME-output
      .
    • docker push $ECR_ENDPOINT/cache-registry:$APP_NAME-output
      when:
      branch:
      • develop
      • release/next
        event:
      • push
      • pull_request
        services:
  • name: docker
    image: docker:19.03.14-dind
    pull: if-not-exists
    privileged: true
    volumes:
    • name: dockersock
      path: /var/run