🧭
Hosting

Portainer: Managing Docker from Your Browser

18.11.2026
← All articles

Docker is powerful on the command line, but typing docker ps, docker logs and long compose commands every day is not for everyone. Team members with little Linux experience end up waiting for an admin just to restart a container or read a log. Portainer solves this by presenting Docker in a clear web interface.

What Portainer can do

Portainer is itself a web app running in a container. It connects to the Docker daemon and lists every container, image, volume and network, showing status, memory and CPU use and published ports. You can stop, restart, read logs or open a console with one click. The Stacks section lets you paste a Docker Compose file, launch a whole project and edit it in place. The free Community Edition (CE) is enough for small and medium setups; advanced access control and enterprise features are in the paid Business Edition.

Installing on a VPS

With Docker already running, create a volume and a container. Here the UI is bound to localhost only, for reasons explained below.

docker volume create portainer_data

docker run -d   --name portainer   --restart=always   -p 127.0.0.1:9443:9443   -v /var/run/docker.sock:/var/run/docker.sock   -v portainer_data:/data   portainer/portainer-ce:lts

Create the admin account within a few minutes of starting; if the setup window times out, run docker restart portainer.

Accessing the interface safely

Portainer talks to /var/run/docker.sock, and access to that socket is effectively root on the server, since anyone with it can start a container with full access to the host file system. Leaving Portainer open to the internet, especially with a weak password, is a serious risk. The simplest safe option is an SSH tunnel:

ssh -L 9443:localhost:9443 admin@server.example.uz
# then open https://localhost:9443

Portainer uses a self-signed certificate by default, so the browser will warn you, which is acceptable over a tunnel. If your team needs a permanent URL, put it behind a reverse proxy such as Caddy or Nginx on portainer.example.uz with Let's Encrypt, a strong password and ideally an IP allowlist.

Everyday tasks

Example: a training center's server

A training center in Namangan runs its website, an online testing system and a Telegram bot in Docker on one VPS. An outside developer set it up, and the center's staff member knows little Linux. When the bot stopped, he used to call the developer and wait. Now he has rights to view and restart only the relevant containers, so he reads the bot's logs in the browser and either restarts it or forwards the error. The developer keeps compose files as stacks and manages updates in one place.

Limits and precautions

Portainer is not a backup system, and deleting a volume by accident is as easy as deleting a container, so back up databases, uploads and the portainer_data volume separately. Update Portainer like any image: pull the new image, remove the container and recreate it with the same volume, and your settings remain.

docker pull portainer/portainer-ce:lts
docker stop portainer && docker rm portainer
docker run -d --name portainer --restart=always   -p 127.0.0.1:9443:9443   -v /var/run/docker.sock:/var/run/docker.sock   -v portainer_data:/data   portainer/portainer-ce:lts

On a sayt.uz VPS, Portainer makes day-to-day management much easier, but think carefully about who gets access. Configured well, it gives each team member exactly the rights they need and saves the admin's time.

Related articles

🧭 Self-Hosting a Vector Database: Qdrant and pgvector 💾 How to Restore a Site and Database from Backup in ISPmanager 🤝 Reseller hosting in Uzbekistan: hosting client sites the organised way 🐳 Running Multiple Projects on One VPS with Docker
🌐 Language
🇺🇿 O'zbek 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓