sync is broken on local cluster

[dgageot]

Sync is broken when images have not been pushed.

The code now tries to retrieve the remote image to check the working dir.
Because the image was never pushed, this fails hard.

[antl3x]

same here!

FATA[0034] calling final callback: sync: retrieving working dir for hub-api:b5f8168bb1bc595174f01810d8e3cc47cf9bc22404b4253e2baf77baf63b83c1: retrieving remote config: UNAUTHORIZED: "authentication required"

[ayyazzafar]

same here!

FATA[0034] calling final callback: sync: retrieving working dir for hub-api:b5f8168bb1bc595174f01810d8e3cc47cf9bc22404b4253e2baf77baf63b83c1: retrieving remote config: UNAUTHORIZED: "authentication required"

@aasm-moura did you get any solution for this issue? I am also facing same problem.

[antl3x]

@ayyazzafar we have disabled the sync until the new skaffold release.

UPDATE: Have downloaded the latest release and it works!

Link: https://storage.googleapis.com/skaffold/builds/latest/skaffold-darwin-amd64

[paulohac]

Still facing the same issue with the latest release 0.24.0

[ghost]

I'm encountering the same issue on 0.24.0.

[adrian-gl]

I'm encountering the same issue on 0.24.0.

same here :(

[jasonwc]

Just ran into the same thing on edge:

> skaffold version
7152e30

apiVersion: skaffold/v1beta7
kind: Config
build:
  artifacts:
  - image: phoenix-no-db-no-docker
    docker:
      dockerfile: Dockerfile.local
    sync:
      'lib/**/*' : /app/lib/
  local:
    push: false
deploy:
  kubectl:
    manifests:
    - deployment.yml

Specifically, trying to use skaffold with microk8s docker registry without specifying it as the remote docker repository (e.g. image: localhost:32000/phoenix-no-db-no-docker)

Use case is that atm we've got devs on Mac using Docker for Mac and Devs on Linux using microk8s. Would like to be able to provide a universal skaffold.yml for both machines that just uses the appropriate docker sock. Instead I'm setting the DOCKER_HOST appropriately on each machine type.

Running on edge because syncing was broken for my use case until #1813 makes it into a release