Fabian Kramm

@AskAlice thanks for creating this issue! Looks like the `tar` command is not present in the target container, but it is required for the sync to function correctly. Could that...

@JamesHutchisonCarta thanks for creating this issue! Could you retry this with the new v6.0.0-alpha version? I suspect it should be fixed there already.

Mhh seems like capabilities is not correctly working if `helm template` is used, seems like we need to change the component chart for this

@tukobadnyanoba thanks a lot for the issue! Yes you are totally correct, we need to exclude those for our quickstart projects

@CiiDyR thanks for the issue! After internal discussions we have decided to add the `--set` flag to `run_default_pipeline` as well as `run_pipelines` that modifies the current config that will be...

@johnnypea maybe try to use `imagePullPolicy: Never` as this might help

Ah yeah, since minikube has its own docker daemon, devspace pushes the image to docker instead of the minikube daemon, which is why the image cannot be pulled. A workaround...

@johnnypea not sure but I believe pushing the image still doesn't reach the correct docker daemon

@edim24 thanks for opening this PR! Could you share your `devspace.yaml` please? What happens if you do a `devspace purge` and `devspace dev -b -d`?

@edim24 thanks for the information! I guess the problem is the `image: example.com/node:${TAG}`, you need to specify it like this: ```yaml images: node: image: example.com/node tags: ["${TAG}"] build: disabled: true...