Waterfront Deployments
Ship containers to industrial PCs and servers, x86‑64 or ARM, and start them from your browser.
Fig. 1Hardware the mutexer agent runs on, by architecture. Push a multi-architecture image and each device pulls the variant for its own processor; any Linux device on these architectures will do.
Point a program at an image on Docker Hub, Amazon ECR, Azure Container Registry or your own registry, choose the tag, and deploy.
Registry credentials live in Strongroom Secrets Management and are resolved when a deploy runs, never pasted into a script.
Every program belongs to a device. Deploy it, stop it, start it or remove it from the same tree you use to find it.
A deploy goes out only when the device is online. Nothing waits silently for a machine that's gone dark.
Docker on the device pulls the variant that matches its architecture: x86-64, 64-bit ARM or 32-bit ARMv7.
The device reports each step as it takes it: received, pulling, stopping the old container, starting the new one. Pull and login errors come back straight away and mark the deploy failed.
Each deploy stops and replaces the previous container, so a program never runs twice on the same machine.
Secrets bound to the program in Strongroom become environment variables when the container is created, so they never sit in an image layer.
Containers restart if they exit or the device reboots. Start, stop or remove a program from the browser.
Open a program and read what it's saying: the latest thousand lines, then each new one a second or two after the container writes it.
The agent follows each container's output through Docker on the device. No logging library to add and no code to change.
When a deployment completes, the program's output opens on its own. The first line you see is your container starting.
If the device loses its connection, it resumes from where it left off on reconnect, as long as Docker on the device still holds the lines.
Container deployments and live output for field-deployed devices.
| Workload | Container images |
| Container registries | Docker Hub, Amazon ECR, Azure Container Registry, custom |
| Registry credentials | Strongroom, resolved at deploy |
| Architectures | x86-64, ARM64, ARMv7 |
| Deploy target | One device per program, online at deploy |
| Deploy status | Step by step from the device, with failures reported |
| Program control | Start, stop, remove |
| Restart policy | Always |
| Networking | Host network |
| Secrets | Strongroom, as environment variables at container start |
| Container output | Latest 1,000 lines, then live |
| Device runtime | mutexer agent |
| Supported devices | Any Linux device the mutexer agent runs on |
Choose an image, deploy, and read the container's first line of output moments later. In every mutexer project.