<#1043 fix: remove stale devbox container on resta...
# flyte-github
a
#1043 fix: remove stale devbox container on restart Pull request opened by pingsutw Summary Screenshot 2026-05-07 at 10 37 54 AM • Fix
container name "/flyte-devbox" is already in use
error when running
flyte start devbox
after the container exists in a stopped/exited state (e.g. after Docker Desktop or machine restart). •
_container_is_running
only checks running containers via
docker ps
, so a stopped container would fall through to
docker run
and fail on the name conflict. • Always run
docker rm -f flyte-devbox
(with
check=False
) before starting, so any leftover container — running or stopped — is cleared. The "already running" prompt is preserved. Test plan •
flyte start devbox
, then restart Docker, then
flyte start devbox
again — should start cleanly instead of erroring. •
flyte start devbox
while one is already running, answer
y
to the prompt — should remove and recreate. • Fresh machine with no existing container — should start normally. flyteorg/flyte-sdk