Build and run containers in workspaces
Build and run container images in OpenShift Dev Spaces workspaces using fuse-overlayfs for Podman and Buildah, and kubedock for Testcontainers and similar frameworks.
- How fuse-overlayfs works in Cloud Development Environments
By default, newly created workspaces that do not specify a devfile use the Universal Developer Image (UDI). The UDI contains common development tools and dependencies commonly used by developers. - Access /dev/fuse in workspace containers
Access/dev/fusein workspace containers to use fuse-overlayfs as a storage driver for Podman. - Enable fuse-overlayfs with a ConfigMap
Enable fuse-overlayfs as the storage driver for Podman and Buildah by mounting astorage.confConfigMap into all workspaces in your project. - How kubedock works
Kubedock is a minimal container engine implementation that gives you a Podman-/docker-like experience inside an OpenShift Dev Spaces workspace. - Enable kubedock in a workspace
Enable kubedock in an OpenShift Dev Spaces workspace by adding environment variables to the devfile. - Use Kubedock in a workspace
Use Kubedock to run containers in your workspace when Docker-in-Docker or privileged containers are not available.