Fail to start dev container since v0.230

Since the udpate to 0.230, Zed cannot create dev containers anymore. It fails with the following message:

> 2026-04-27T21:32:44+02:00 WARN [dev_container::devcontainer_manifest] No initialize command found
2026-04-27T21:32:49+02:00 ERROR [dev_container::docker] Non-success result from docker pull: Trying to pull localhost/gtkrus-77c22ef7508d8062-features:latest...
time="2026-04-27T21:32:46+02:00" level=warning msg="Failed, retrying in 1s ... (1/3). Error: initializing source docker://localhost/gtkrus-77c22ef7508d8062-features:latest: pinging container registry localhost: Get \"https://localhost/v2/\": dial tcp [::1]:443: connect: connection refused"
time="2026-04-27T21:32:47+02:00" level=warning msg="Failed, retrying in 1s ... (2/3). Error: initializing source docker://localhost/gtkrus-77c22ef7508d8062-features:latest: pinging container registry localhost: Get \"https://localhost/v2/\": dial tcp [::1]:443: connect: connection refused"
time="2026-04-27T21:32:48+02:00" level=warning msg="Failed, retrying in 1s ... (3/3). Error: initializing source docker://localhost/gtkrus-77c22ef7508d8062-features:latest: pinging container registry localhost: Get \"https://localhost/v2/\": dial tcp [::1]:443: connect: connection refused"
Error: unable to copy from source docker://localhost/gtkrus-77c22ef7508d8062-features:latest: initializing source docker://localhost/gtkrus-77c22ef7508d8062-features:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused
\
2026-04-27T21:32:49+02:00 ERROR [dev_container::devcontainer_manifest] Non-success status from docker run. StdErr: Error: statfs /home/titouan${localEnv:USERPROFILE}/.config/fish: no such file or directory
\
2026-04-27T21:32:49+02:00 ERROR [recent_projects::remote_servers] Failed to start dev container: DevContainerUpFailed("Failed with nested error: CommandFailed(\"podman\")")

I have not made any change to the app permission.

Downgrading to v0.229 fixes the issue.

Start by reproducing dev-container startup on v0.230 and compare it with v0.229, using the reported Docker pull and missing fish-directory errors as checkpoints. Trace the dev-container startup path responsible for those commands; done means the affected container starts successfully without either failure.

Written by the indexing model from the issue text.