Resume the previous sandbox

Describe the feature/command for FlyteCTL

I created a sandbox using: flytectl sandbox start --source, and I can access Flyte UI. However, after stopping the container and starting the Docker container to resume the existing sandbox container, I can’t access the Flyte UI.

I could run flytectl sandbox start --source and rebuild the container again, but it often takes a long time to start a container. By resuming the container, I can start the container quickly and keep my previous experiments in flyte’s sandbox. I wonder if there is any way you can add a feature that allows users to resume a sandbox container?

The command line can look something like this:

$ flytectl sandbox resume

Provide a possible output or UX example

All of my previous activities in the sandbox are resume.

Are you sure this issue hasn’t been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[jeevb]

@jeevb log of /var/log/dockerd.log

failed to start daemon: pid file found, ensure docker is not running or delete /
var/run/docker.pid

I think we need a check for PID in entrypoint script.

Makes sense to skip starting dockerd and k3s if they are already up!

[jeevb]

@jeevb we might need to make the flyte-entrypoint.sh restartable so that we can essentially restart all k3s and flyte services, but restore the state of db’s

I imagine we can do this by using a docker volume + hostpath volume for the postgres container.