Russell Centanni

@afreyermuth98 Could you share your `devspace.yaml`? Here's a very simple example that works with `devspace deploy` & `devspace purge`. You might also check to see whether the namespace being used...

@kuuji Thanks for submitting this issue! Yes this does seem odd, and the recommended usage is to use `devspace use namespace [NAMESPACE]` before running `devspace deploy`. This results in updating...

@kuuji Ah I see, I skimmed over the incluster part. I'm surprised that setting the `namespace` in the deployment config didn't work. We'll take a look, but it may be...

@lee-aaron Hello! It looks like our new local registry feature is interfering with your existing registry. Could you try disabling it by adding this to your `devspace.yaml` config? ```yaml localRegistry:...

@lee-aaron It also looks like DevSpace wasn’t able to find your registry credentials according to: ``` Couldn't retrieve password for registry DESKTOP-R2R7EL6:5000 from docker store ``` Is this a registry...

@lee-aaron Looks like it's unrelated to the new local registry feature since you were able to turn that off. Are you able to build the image using `docker` by itself?...

@lee-aaron Have you tried with the latest version of DevSpace? Some of our recent fixes might help with this.

@jackwilsdon Thanks for the analysis! We will take a look at a fix. I had previously assumed that this was an issue with the library we were using for the...

@jackwilsdon While not a solution for this particular problem, I've found that `read -p "Some prompt here: "` works as expected in [commands](https://www.devspace.sh/docs/configuration/commands/). The read values can then be passed...

FWIW, there is [devpod.sh](https://devpod.sh/) now. Closing since DevSpace will remain Kubernetes specific.