Launcher · Workflow

Switch Between SD · Jupyter · DeepSpeed

Launcher, not SSH: everything lives behind powered doors.

Overview

CloudDock doesn’t want you juggling ports, SSH sessions, and “which tab is which machine.” Instead, each container has a CloudDock Launcher — a consistent home screen that opens the right tools for that container.

Key idea: you don’t “SSH into apps.” You switch containers, and the Launcher follows you.

Universal containers: SD + Jupyter (daily workflow)

Universal Usagi / Momonga are built for Stable Diffusion creators. They include:

  • Stable Diffusion (A1111)
  • JupyterLab
  • CloudDock App Store
  • and the same CloudDock Launcher to open them
CloudDock Launcher inside Universal container showing SD, Jupyter, App Store, Training Center
Universal = the SD-first cockpit: SD + Jupyter + training workflow.

Why DeepSpeed is a separate container

Deep learning tooling and SD tooling look similar on the surface, but they serve different users:

  • Universal focuses on image generation: iterate fast, create, train SD models, follow tutorials.
  • DeepSpeed container focuses on deep learning workloads: LLM training/inference workflows, consoles, and heavier dev tools.

We keep them separate for two reasons:

  • Different audiences — SD creators and DeepSpeed/LLM users are usually not the same crowd.
  • Smaller images — splitting the stacks reduces container size, boot time, and maintenance complexity.
Translation: we don’t force everyone to download and maintain everything. You choose the workflow you need.

How to switch to CloudDock DeepSpeed (step-by-step)

DeepSpeed is not an “app inside Universal.” It’s a separate container. To switch, you will go back to the Dashboard and restart into the DeepSpeed image.

  1. Go back to the CloudDock Dashboard (the machine control page).
  2. Click Restart container (or the equivalent restart action).
  3. Select CloudDock DeepSpeed as the container image.
  4. Read the warning: restarting a container wipes the session. (Yes — data inside the container will be lost. This is expected behavior.)
  5. When prompted, type Confirm in the input box (case-sensitive).
  6. Wait for the restart to complete.
  7. Click Continue to enter the new container.
Important: Restarting a container resets the environment. Any unsaved work inside the container will be lost. If you need persistence, save/export to a mounted workspace or external storage before switching.
CloudDock dashboard showing restart container flow with Confirm input box
Container switching happens in the Dashboard: select image → type Confirm → restart.

What changes after switching

Once you enter the DeepSpeed container, you’ll see something familiar: an identical CloudDock Launcher.

But the buttons reflect the DeepSpeed workflow:

  • JupyterLab
  • DeepSpeed Console
  • CloudDock App Store
  • (No Stable Diffusion button) — because this container is not SD-focused.
CloudDock Launcher inside DeepSpeed container showing JupyterLab, DeepSpeed Console, App Store
Same Launcher design, different doors: DeepSpeed container focuses on ML tooling, not SD.

How to go back to Stable Diffusion

To return to SD, you’ll do the same process in reverse:

  1. Go back to the Dashboard.
  2. Restart container and select Universal Usagi or Universal Momonga.
  3. Type Confirm (case-sensitive) and restart.
  4. Click Continue → you’re back in the Universal container with SD.
Think of it like switching workspaces: Universal = SD studio. DeepSpeed = deep learning lab.

Why A group doesn’t have the DeepSpeed container

You might notice: A group machines do not offer the CloudDock DeepSpeed container. This is intentional.

  • A group is optimized for SD creators and lightweight workflows.
  • DeepSpeed workloads are heavier — they typically demand more VRAM headroom, memory bandwidth, and longer sustained runs.
  • To keep A group fast, cost-efficient, and beginner-friendly, we focus A group on the Universal SD workflow instead of shipping every heavy stack everywhere.
In short: A group is the “best value SD lane.” DeepSpeed is a specialized lab — it belongs on higher tiers where it actually makes sense.

FAQ

“Why do I have to type Confirm?”

Because switching containers is destructive to the current session. The Confirm step prevents accidental restarts (and accidental data loss).

“Why is the Launcher the same in both containers?”

Consistency. You shouldn’t have to relearn navigation just because you changed workflows. The doors change; the hallway stays the same.

“So restarting always wipes everything?”

Yes, the container session resets. Treat the container like a disposable workspace. Save/export important work before switching images.

What’s next?

Powered doors. Same hallway.