---------------------- I'm sorry to hear that you're experiencing issues with the

deploy --sync

command. The error message suggests that the synchronization from the build path to the Build sync Pod failed to start. Here are a few steps you can try to resolve this issue: 1. **Restart the sync daemon**: If you're using Garden version

0.13.26

or later, you might need to stop all syncs and the sync daemon before running the

deploy --sync

command. You can do this by running the following commands from the project root directory:

bash
GARDEN_ENABLE_NEW_SYNC=false garden util mutagen daemon stop
GARDEN_ENABLE_NEW_SYNC=true garden deploy --sync

This will stop the old sync daemon and deploy with the new sync mode. If you're using a version earlier than

0.13.33

, replace

true

with

false

in the second command. [^1^] 2. **Check your configuration**: Ensure that your

Deploy

action is correctly configured for code synchronization. For example, if you're using the Kubernetes plugin, your configuration might look something like this:

yaml
kind: Deploy
type: kubernetes
name: api
---
spec:
  defaultTarget:
    kind: Deployment
    name: api
  sync:
    paths:
      - containerPath: /app/src
        sourcePath: ${actions.build.api.sourcePath}/src
        mode: two-way

In this example, code synchronization is set up from the

api

Build action's directory. [^2^] 3. **Update Garden**: If you're using an older version of Garden, consider updating to the latest version. There have been several updates and bug fixes related to code synchronization in recent versions. If none of these steps resolve your issue, please consider reporting it on the Garden GitHub page () or the Garden Discord server () for further assistance.

[^1^]: () [^2^]: () ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted