Next.js + TypeScript
The application is built with Next.js, React, and TypeScript, with Tailwind CSS handling the interface.
$cat README.md↳01 / OVERVIEW
Containo
A self-hosted web application for managing Docker containers, images, volumes, and stacks from a single interface.
TYPEAcademic Project
ROLEFull-stack
PERIODMay 2026–Present
LINKS
TECHNOLOGY STACK
Next.jsReactTypeScriptSQLiteDockerDockerodeWebSocketTailwind CSS
~/home/projects/containo[ 01 / 05 ]docker / managementpreview
ASSETS / SCREENSHOTS
↳02 / CONTEXT
The context
Containo is a web-based Docker management application developed as part of a mandatory Penulisan Ilmiah project during the sixth semester.
The project started from a simple idea: managing Docker does not always need to happen through the command line. Containo brings common Docker operations into a single web interface for a single host.
Development started in May 2026 and is still ongoing, with the project being maintained and improved as the application evolves.
↳03 / WHAT I DID
What I did
/frontend
Built the interface with Next.js, React, TypeScript, and Tailwind CSS.
/backend
Implemented application logic and API routes for Docker management and user authentication.
/docker
Connected the application to Docker Engine through Dockerode and the Docker socket.
/storage
Implemented SQLite for storing application account and authentication data.
/features
Built workflows for container, image, volume, stack, monitoring, and volume backup and restore.
↳04 / UNDER THE HOOD
Under the hood.
Docker Engine integration
Dockerode is used to communicate with Docker Engine and handle common container, image, volume, and stack operations.
Docker socket
The application connects to the host Docker Engine through the Docker socket when running as a container.
SQLite
SQLite is used for application-level data, including user accounts and authentication information.
Host monitoring
The dashboard provides basic information about CPU, memory, storage, and Docker Engine status.
Single-host setup
Containo is designed to work with a single Docker Engine rather than a multi-host orchestration environment.
↳05 / NOTES
Notes
What changed
The project grew from a basic Docker interface into a broader management application covering common container, image, volume, and stack workflows.
What I learned
The project became a practical way to learn how a web application can interact with Docker Engine and turn command-line workflows into a graphical interface.
What I'd do differently
Keep the core scope focused while continuing to improve the parts of the application that are used most often.