Skip to content

In a Nutshell (🌰)

  • View all Docker containers across your devices
  • Deploy containers from templates or custom configurations
  • Start, stop, restart, and remove containers
  • View container logs and resource usage
  • Manage Docker images, networks, and volumes

Container Overview ​

SSM provides a centralized container management interface that allows you to monitor and control Docker containers across all your connected devices. SSM automatically discovers and lists running Docker containers from all connected and configured devices, actively monitors Docker events in real-time to keep its information current, and also performs a periodic full scan (hourly by default) to ensure synchronization with your devices. The Containers tab gives you a comprehensive view of your containerized applications.

Containers Dashboard
The Containers dashboard showing all containers across devices

Key Features ​

The container management interface offers:

You can typically find a 'Force Refresh' button (often depicted in images like the one for Docker Image management below) to update the view and check for new image versions.

Container Update Detection ​

SSM helps you keep your containers up-to-date. It can detect when a newer version of a container's image is available in its source registry. An 'Update available' tag or indicator (as seen in the Docker Networks/Volumes images below, for example) will be displayed next to the container.

The update detection mechanism primarily works by comparing semantic versioning (semver) strings, typically in the MAJOR.MINOR.PATCH format. SSM attempts to parse these versions strictly and includes a fallback to handle less standard versioning by focusing on the core segments.

This feature often relies on container labels, similar to systems like WhatsUpDocker. For detailed information on how labelling works and how to configure it for update detection, see the Container Labelling Guide.

If your container images are stored in a private registry, ensure you have configured private registry authentication in SSM settings to enable update checking for these images.

Container Details ​

Click on a container to view detailed information:

TODO IMAGE

The details panel shows:

  • Configuration: Environment variables, volumes, networks
  • Metadata: Labels, container ID, creation time

Managing Containers ​

Container Actions ​

For each container, you can perform several actions:

Container Actions
Performing actions on containers

Available actions include:

ActionDescription
StartLaunch a stopped container
StopGracefully stop a running container
RestartStop and restart a container
Pause/UnpauseTemporarily suspend container execution
RemoveDelete the container (optionally with volumes)
View LogsSee container output and error logs
InspectView detailed container configuration

Deploying New Containers ​

SSM offers several ways to deploy new containers:

  1. From Templates: Use pre-configured container templates
  2. Custom Configuration: Create containers with custom settings
  3. Docker Compose: Deploy multi-container applications

Deploying from Templates ​

The easiest way to deploy a container is from the templates store:

  1. Navigate to the Containers tab
  2. Click "Deploy from Store"
  3. Browse or search for a template
  4. Configure the container settings
  5. Click "Deploy"
Deploy from Store
Deploying a container from the template store

Learn more about deploying from the store.

Working with Networks and Volumes ​

SSM provides interfaces for managing Docker networks and volumes:

TODO IMAGE

For networks, you can:

  • Create custom networks
  • Connect containers to networks
  • View network details and connected containers
  • Remove unused networks

TODO IMAGE

For volumes, you can:

  • Create new volumes
  • Browse volume contents
  • Back up volume data
  • Remove unused volumes

Container Stacks ​

For more complex applications with multiple containers, SSM provides the Container Stacks feature:

Container Stacks
Managing container stacks

Learn more about using Container Stacks.

Troubleshooting Containers ​

Issue TitleSymptomsSolutions
Container Fails to Start- Container status is Exited or Error
- No logs or error messages shown
- Check container logs for errors
- Verify image name and tag are correct
- Ensure required environment variables are set
- Check for port conflicts or missing volumes
Cannot Access Service in Container- Service not reachable at expected port
- Connection refused or timed out
- Check container port mappings
- Verify service is running inside the container
- Check firewall rules on host and container
Container Uses Excessive Resources- High CPU or memory usage
- Host system becomes slow or unresponsive
- Limit resources using Docker Compose or container settings
- Monitor container stats and adjust limits as needed
- Restart or scale down containers if necessary

Next step

âžĄī¸
Deploy From Store

Deploy a container

→

Made with love