Tutorials · DevOps & Containers
Docker Basics on a NavEdge Edge Server: Run Your First Container
NavEdge edge servers run on-site applications in Docker containers. Learn the five commands you need: pull, run, ps, logs and restart policies.
Before you start
- A NavEdge edge server or any Linux host with Docker Engine
- SSH access with your own key
- Internet access to a container registry
Step by step
Check Docker
Confirm the engine is running and your user may use it.
docker version docker info --format '{{.ServerVersion}} {{.Driver}}'
Pull an image by version
Always pin a version tag instead of latest, so every site runs the same software.
docker pull nginx:1.27-alpineRun it
Give the container a name, publish a port, and set it to restart after a reboot or crash.
docker run -d --name web --restart unless-stopped -p 8080:80 nginx:1.27-alpineCheck it
List containers, read the logs and test the port.
docker ps docker logs --tail 50 web curl -I http://localhost:8080
Update it
Pull the new version, remove the old container and start the new one. Data in volumes is kept.
docker pull nginx:1.27.3-alpine docker rm -f web docker run -d --name web --restart unless-stopped -p 8080:80 nginx:1.27.3-alpine
Clean up
Remove unused images to keep the edge server's disk free.
docker image prune -a --filter "until=168h"
Commands are generic, industry-standard examples. Exact syntax and menu names vary by model and firmware; check your device's manual on the Documentation page.
Pro tips
- Keep application data in named volumes or bind mounts, never inside the container.
- Use docker compose (next tutorial) as soon as you have more than one container.
FAQ
Frequently asked questions
Container or virtual machine?
Containers share the host kernel, start in seconds and use far less memory, which suits small edge servers. Use a VM when you need a different OS.
Keep learning
Related guides
Docker Compose for edge applications
Read more →Secure containers on the edge
Read more →How to Use SSH Keys Instead of Passwords for Network Devices and Servers
Passwords can be guessed, phished and reused. Create an SSH key pair, install the public key on gateways, edge servers and Linux hosts, then turn password logins off.
Read more →How to Reach Remote Sites Safely With an SSH Jump Host
Do not expose SSH on every device. Put one hardened jump host (bastion) in front of the management network and reach everything else through it.
Read more →How to Open a Device Web Page Through an SSH Tunnel
Reach the web interface of a switch, NVR or container on a remote site without opening a firewall port: forward it through SSH.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.