Russell Centanni

Thanks for creating this issue. Does this container run as a non-root user that may not have permissions to create the `.devspace` directory? I suspect your Dockerfile workaround works since...

@frank-bee Currently, yes it's required to run the `ghcr.io/loft-sh/devspace-containers/typescript:18-alpine` image as root to avoid this issue. This image is provided for convenience, but if you have restrictions that prevent you...

Hello! The `[name]` part refers to the name of the `dev` configuration, so for your `dev.app.sync` configuration, you should be able to target that specific one with `before:initialSync:app`. The sync...

I tried the following `hooks` config in `devspace.yaml` ```yaml hooks: - events: ["before:initialSync:app"] command: "env | sort" ``` And it shows the `$DEVSPACE_HOOK_SYNC_CONFIG` environment variable in the output: ```shell dev:app...

@mwagner5310 It sounds like the container might be restarting before the sync can complete. `devspace sync` won't override the container entry point like `devspace dev` typically does IIRC. If the...

It's been a bit since I've used the persistence options, so `devspace purge` may clean up the PVC. Have you tried it? Even if it does not, the `purge` pipeline...

Hello! You can re-map the local port to avoid the conflict: ```yaml ... dev: api: imageSelector: traefik/whoami ports: - port: "8091:8090" ``` Hope that helps!