Docker quick start

The BeAdmin panel can install Docker on the server — a service for running applications in isolated containers — and manage it from the panel UI. The module supports pulling images, creating containers, and managing their lifecycle. There is no need to learn the CLI, manage socket permissions, or install Docker by hand.

Install the module

Open Docker in the side menu and click "Install". Installation takes a few minutes — the progress is shown in the logs. Once installed, the module page exposes the "Containers" and "Images" tabs. If installation fails, try running it again: another process may have prevented the package manager from completing the task.

Images

An image is a template containers are created from: it bundles an application together with its environment. Before creating a container, pull at least one image to the server — from the public Docker Hub registry or any other registry the server can reach. Pulled images are stored locally and become available when creating a container.

1. Switch to the "Images" tab and click "Pull image".
2. In the "Pull image to server" dialog, enter the image name in the name:tag format in the "Name" field, for example ubuntu:latest.
3. Click "Pull".

The image will appear on the "Images" tab.

Create a container

A container is a running instance of an image: an isolated environment where the application runs with its own process, file system, and network settings. Any number of containers can be created from a single image — each with its own name, startup command, and restart policy.

1. On the "Containers" tab, click "Create container".
2. Fill in the fields:
   • "Name" — Latin letters, digits, and the symbols _, ., -. If left empty, the name is assigned automatically. If the name is invalid, the panel will show an error.
   • "Image" — pick a previously pulled image from the list. If the image you need is not there, you can pull it without leaving the form — the button next to the field opens the same dialog as on the "Images" tab.
   • "Working directory" — folder inside the container where commands run by default. For example, /app.
   • "Restart policy" — Docker behavior when the container stops.
   • "Remove after exit" — automatically remove the container after it stops.
   • "Command" — what to run on start. If left empty, the command from the image is used.
   • "Entrypoint" — set this if a custom startup logic is needed.
3. Click "Create".

The new container will appear in the list on the "Containers" tab with its state and startup parameters.

Manage a container

A container can be in one of four states: created, running, stopped, or paused. You can move it between states right from the container list: each row exposes start, stop, pause, and restart buttons. The available actions depend on the current state — for example, "Start" is available for a stopped container, "Resume" only for a paused one.

From a container row you can also rename or delete the container. Deletion loses the data inside the container; volumes and the source image stay on the server.

⚠️ Deleting a running container

By default, only stopped containers can be deleted. To delete a running one, enable "Force delete" in the dialog — Docker will stop and remove the container in one step, without an extra click.