Container Deployment
Run your own container workloads directly on the edge with Portainer, a web-based container management interface built into every mrxnode device. This guide walks you through deploying and managing containers on your device.
Overview
Each mrxnode device includes Portainer CE, a web-based container management interface. You can deploy and manage Docker containers directly on your edge device, alongside the Mirox-Agent workloads.
Accessing Portainer
Portainer is available on your mrxnode's IP address:
| Protocol | Port | URL |
|---|---|---|
| HTTPS | 9443 | https://<device-ip>:9443 |
Self-Signed Certificate
The HTTPS port uses a self-signed certificate. Your browser will show a security warning - this is expected. You can proceed by accepting the certificate.
Login with the appuser credentials (see mrxnode Overview for password information).
Deploying Containers
Using the Web Interface
- Open Portainer in your browser
- Navigate to Containers in the left sidebar
- Click Add container
- Configure your container:
- Name: Give your container a descriptive name
- Image: Enter the Docker image (e.g.,
nginx:latest,redis:alpine) - Ports: Map container ports to host ports
- Volumes: Mount persistent storage (see below)
- Click Deploy the container
Pulling Images
Portainer can pull images from:
- Docker Hub (public images)
- Private registries (configure credentials in Portainer settings)
Persistent Storage
Containers are ephemeral by default - their data is lost when they stop or restart. To persist data across reboots and system updates, use Docker volumes.
Creating a Volume
- Go to Volumes in the left sidebar
- Click Add volume
- Enter a name for your volume
- Click Create the volume
Mounting Volumes to Containers
When creating or editing a container:
- Scroll to the Volumes section
- Click map additional volume
- Select your volume and specify the container path (e.g.,
/data) - Deploy or update the container
Persistent Data
Data stored in mounted volumes survives:
- Container restarts
- Device reboots
- System updates
Best Practices
- Resource limits: Set memory and CPU limits to prevent containers from consuming all device resources
- Auto-restart: Enable restart policies for containers that should run continuously
- Logging: Configure log rotation to prevent disk space issues
- Security: Only deploy trusted container images
Further Information
For detailed Portainer usage instructions, refer to the official documentation:
Related Features
- mrxnode Overview — device setup, registration, and SSH access
- Command Cheatsheet — quick reference for common device commands
- How-To Guide — network and disk tasks on your device
- Troubleshooting — recovery patterns when the device misbehaves