Skip to content

Add a Docker Sandboxes content kit as a second way to run the lab - #4

Open
mathieu-benoit wants to merge 2 commits into
mainfrom
sbx-content-kit
Open

mathieu-benoit wants to merge 2 commits into
mainfrom
sbx-content-kit

Conversation

@mathieu-benoit

@mathieu-benoit mathieu-benoit commented Nov 18, 2026 •

Copy link
Copy Markdown
Owner

What

Adds a Sandbox Kit for this lab, following the layout in mathieu-benoit/labsbxes examples/. It runs with the labsbxes Labspace kit as a second option, next to the Compose one:

sbx run shell --kit ghcr.io/mathieu-benoit/labsbxes/labspace:0.1.4 --kit ghcr.io/mathieu-benoit/labsbx-dhi-launch:0.1.0 -p 8085:8085 -p 5001:5001 --name dhi-launch -d
  • dhi-launch.yaml: the kit descriptor (mixin). It requires labspace >= 0.1.0, provides labspace-content, publishes port 5001 (the "App" tab) and allows the egress the lab needs beyond Docker Hub pulls: docker login, dhi.io, Docker Scout, ghcr.io and PyPI.
  • dhi-launch.dockerfile: copies labspace/ and project/ to /opt/labspace/content, plus the Docker Scout CLI plugin (docker/scout-cli:1.29.0). The sbx shell agent has no docker scout, and the lab relies on docker scout compare.
  • .dockerignore: keeps the kit's build context to the lab content. It doesn't affect the dinner image, which builds from project/.
  • .github/workflows/publish-kit.yaml: on every push to main (or a manual run on main), publishes ghcr.io/<owner>/labsbx-dhi-launch as :latest and :sha-<short>, plus :<version> from dhi-launch.yaml the first time that version is published (never overwritten). Pull requests only build and validate with kit-tck.
  • README.md: new "Run this Labspace in a Docker Sandbox (option 2)" section.

Tested

With sbx v0.54 on Windows, the local labsbxes kit and this kit, from an empty folder:

  • Kit builds through the kit frontend (descriptor validated)
  • Interface serves the lab (title and 7 sections), ~/project is seeded
  • docker scout version works in the sandbox
  • docker build (PyPI) and docker compose up -d --build work, and the app answers on localhost:5001 from the host
  • Pulls from ghcr.io/mathieu-benoit/dinner:initial and Docker Hub work, and dhi.io and Scout are reachable

Not tested

  • docker login and the docker scout compare steps (need a Docker account)
  • The published GHCR references: the kit isn't published yet. The merge publishes :0.1.0; then make the new labsbx-dhi-launch package public.

🤖 Generated with Claude Code

mathieu-benoit and others added 2 commits November 17, 2026 23:36
Package labspace/ and project/ as a Sandbox Kit that runs with the Labspace
kit from mathieu-benoit/labsbxes (sbx run shell --kit ... --kit ...). The kit
also ships the Docker Scout CLI plugin (missing from the sbx shell agent),
publishes the app port 5001, and allows the egress the lab needs (Docker
login, dhi.io, Scout, ghcr.io, PyPI). A workflow publishes it to
ghcr.io/<owner>/<repo>/kit; the README documents the option.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Trigger the publish on pushes to main instead of v* tags, and publish to
ghcr.io/<owner>/labsbx-dhi-launch. :latest and :sha-<short> follow main;
:<version> is added the first time that version is published and never
overwritten.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant