Artica for Docker Edition
Artica For Docker Edition lets you build a docker service in just a few clicks. Its aim is to offer system management, maintenance and administration of docker containers.
Run your containerized applications from the Artica web console.
Artica for Docker Edition brings container management, Compose stacks and host administration into one place.
Use it to test an application, run internal services or manage a dedicated Docker host.
Try it on a separate Artica appliance with a small application first.
Check the prerequisites and enable Docker.
Why choose Artica for Docker Edition?
- Handle everyday work in your browser.
Start containers, read logs, inspect resource use and open a terminal from the same console. - Keep application services together.
Compose stacks group an application's containers and configuration for deployment and maintenance. - Review changes before deployment.
Stack analysis identifies unsupported options, permission requirements and security warnings.
Port conflict checks help catch deployment problems before services start. - Share administration with controlled access.
Give operators the Docker permissions they need for their work.
Separate viewing, deployment, console access and destructive actions. - Keep a record of operations.
The Docker audit log helps administrators investigate changes and failed actions. - Use the Artica environment you already administer.
Manage the Docker service alongside the appliance's system tools.
Features
The current Docker Manager provides the following functions.
Availability depends on the installed packages, administrator permissions and enabled components.
| Area | What you can do |
|---|---|
| Service status and engine | Check Docker Manager and Docker Engine status and versions. Install or restart the manager with the required administrator rights. Inspect engine information and configure permitted image sources. |
| Containers | List and inspect containers. Create, start, stop, restart, pause, resume, rename, kill and remove them according to your permissions. Configure ports, mounts, environment variables and resource limits. |
| Logs and troubleshooting | Read container logs and inspect running processes. Use container details to investigate configuration and runtime problems. |
| Browser terminal and commands | Open an interactive terminal in a running container. Run individual commands and view their output. Review and close your terminal sessions. |
| Images | List images, inspect details and view build history. See which containers use an image. Pull, build, tag and remove images. Preview image cleanup before pruning unused images. |
| Image catalog and registries | Browse the curated Store and search Docker Hub or quay.io. Read image information and select tags. Pulling an image remains subject to the configured registry policy. Docker Hub is allowed by default. Other image sources require administrator approval in the image source settings. |
| Downloads and jobs | Follow image pulls, builds and stack deployments. Check operation results and cancel supported jobs with the required permissions. |
| Compose stacks | Analyze and deploy supported Compose configurations. Edit stacks, inspect changes and review revisions. Start, stop, restart or remove a stack. Check image updates and update individual services. Roll back to a previous configuration revision. |
| Import and reuse | Use available Store templates to prepare stacks. Generate Compose configuration from an existing container. Adopt an existing Compose project into stack management. |
| Secrets | Manage stack secrets with a separate permission. Secret values are encrypted in the manager's secret store. Management responses and configuration differences mask their values. |
| Application installers | Use a guided installer where the Store provides one. The Vaultwarden installer prepares a stack with HTTPS, application settings and secrets. |
| Volumes and storage | List and inspect Docker volumes. Remove eligible volumes and prune unused volumes. Use mounts to retain application data beyond the lifetime of a container. |
| Container disk quotas | On installations with the disk quota backend enabled, manage dedicated quota storage for containers. Monitor usage, resize storage and manage its attachment. Backup and restore operations are available through the quota backend. This component requires additional host storage support. |
| Networks | List and inspect Docker networks. Create networks and remove eligible custom networks. |
| Performance and events | Inspect container CPU, memory, network and disk I/O statistics. Follow Docker events to understand lifecycle changes. |
| Permissions and auditing | Assign detailed Docker privileges to administrator groups. Restrict sensitive operations such as privileged container creation and secret changes. Review the Docker audit log. Integration with Artica's administrator tracking requires that tracking to be enabled and the applicable Corporate entitlement. |
| Docker Relay integration | Manage the appliance's Docker Relay agent. Mark supported stack services for publication through an enrolled agent. The relay creates a backend on the Artica reverse proxy. A reverse proxy administrator must attach that backend to a site. |
Where it helps
- For an evaluation environment, start with one container.
Check its logs and resource use, then try a small Compose stack. - For internal applications, use stacks to keep related services together.
Place persistent data in suitable storage and plan application backups. - For teams, grant read access to staff who monitor applications.
Give deployment and terminal permissions to the people who maintain them. - For services published through Artica.
Use the Docker Relay integration with a separate Artica reverse proxy.
Check the relay requirements before planning external access.
Plan your deployment
- Size the appliance for both Artica and your applications.
Images, logs and persistent data consume disk space.
Container networking also depends on the host's firewall and routing configuration. - Compose support validates a defined set of options.
Unsupported options are rejected during analysis.
A configuration rollback does not restore application data.
Keep backups of databases and persistent volumes.
Older releases offered a dedicated Docker Edition activation workflow.
That workflow could disable unrelated Artica services.
Use a separate appliance for your evaluation and review the installation procedure for your release before converting an existing server.
Try Artica for Docker Edition
- Prepare a separate Artica appliance and review the prerequisites and activation steps.
- Install the Docker package if it is missing.
- Enable the Docker service and check that both the engine and manager are running.
- Pull a small image, create a test container and inspect its logs.
- Try a Compose stack, then assign permissions for the administrators who will use it.
On older releases, follow the feature visibility procedure if Docker Edition is hidden.
For older privilege screens, see Docker administration privileges.