Ubuntu-bionic-dind-rootless

Ubuntu Bionic DinD Rootless is a Kasm Workspaces container image that runs a rootless Docker-in-Docker daemon, letting users build and test containers inside…

  • Tools & Utilities
Ubuntu Bionic DinD Rootless is a Kasm Workspaces container image that runs a rootless Docker-in-Docker daemon, letting users build and test containers inside a workspace without privileged host access.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

61/100 Good

Maintained
98last commit 51 days ago
Popular
49272 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
302.70312 GB minimum RAM
GitHub stars
272
Open issues
7
Last commit
2026-10-01
Latest release
29.8.2-r0
License
Apache-2.0
Activity
stale

Checked 15 days ago - source: GitHub (cruizba/ubuntu-dind)

Resources & Compatibility

Minimum requirements: 2.70312 GB RAM, 2 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Secure DinD Prefer the sysbox runtime over --privileged for secure Docker-in-Docker; --privileged is only for dev/testing. source

Fetched 41 days ago - each note links to its source

Alternatives (12)

  • Arch Linux - Arch Linux is a customisable operating system for your computer.
  • CachyOS - CachyOS is designed to deliver lightning-fast speeds and stability, ensuring a smooth and enjoyable computing experience every time you use…
  • CentOS - CentOS Stream is a free, continuous-delivery Linux distribution that provides the upstream rolling build of Red Hat Enterprise Linux (RHEL)…
  • Clear Linux - Clear Linux is a high-performance, rolling-release Linux distribution developed by Intel, now discontinued (end-of-life in July 2025) and n…
  • Debian - Debian is a free, community-maintained Linux distribution that provides a stable base system and package ecosystem for servers, workstation…
  • Fedora
  • Gentoo - Gentoo is a source-based Linux distribution that gives experienced users fine-grained control over which packages are compiled and installe…
  • Kubuntu
  • Linux Mint - Desktop-focused Linux system offering custom menus, multimedia codecs, browser plugins, native DVD playback, and integrated software manage…
  • Manjaro Linux - Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system.
  • Red Hat Enterprise Linux - Red Hat is the leader in development, deployment, and management of Linux and open source solutions for Internet infrastructure - ranging f…
  • Rocky Linux - Rocky Linux is a free, secure operating system designed to run server software.

Checked 40 days ago - source: AlternativeTo

Common questions

Why might an exec session in a rootless Docker container still show root?

An exec session under rootless Docker may report root even when the daemon was installed for a non-root account. The container session can appear to run as root despite the rootless setup.

How should I start a rootless Docker daemon inside another container?

Start dockerd as an unprivileged user in rootless mode. Use the rootless Docker documentation for the exact startup procedure.

Why can docker pull work but docker run fail in a dind container?

docker:dind can have cases where pull succeeds while run fails. dind-rootless may also fail when it is placed on a host that is already using rootless Docker.

Why can rootless DinD fail on Ubuntu 24.04 or later?

On newer Ubuntu versions, rootless DinD can fail because RootlessKit has a requirement that is not satisfied. The article describes the root cause and what actually works in practice.

How does Docker rootless mode differ from userns-remap?

Rootless mode runs both the Docker daemon and containers without root privileges. In userns-remap mode, the daemon still runs with root privileges while containers use user-namespace mapping.

Answers sourced from docs.docker.com, forums.docker.com, forums.docker.com, stackoverflow.com, www.jacobbaek.com

Community

Collected 48 days ago - public community threads