Docker

Docker container remote access - Awacino built in, started on boot

The Awacino Unattended Client as a ready Docker image: one docker compose file, and the host and its network are reachable from anywhere - direct, end-to-end encrypted, without open ports.

Try two slots for freeAlways-on devices
compose.yaml
services:
  awacino:
    image: docker.awacino.net/awacino/unattended:latest
    restart: unless-stopped
    network_mode: host
    pid: host
    privileged: true
    cap_add: [NET_ADMIN]
    environment:
      AWACINO_SETUP_CODE: "YOUR-SETUP-CODE"
    volumes:
      - awacino-data:/opt/awabon
volumes:
  awacino-data:
$ docker compose up -d
The app fills in your setup code. One setup code per device.

Set up in a minute

  1. In the Awacino app: Add unattended device, then Install on NAS.
  2. The app shows your setup code and a compose.yaml with the code filled in.
  3. Start it: docker compose up -d - or paste the file into your NAS's container manager.
  4. The device appears in the app within a minute. The setup code is used once.

The image: docker.awacino.net/awacino/unattended:latest - for linux/amd64 and linux/arm64.

Starts on boot

restart: unless-stopped - the container comes back with Docker after every reboot, and the device is reachable again without anyone logging in.

The host and its network

With the host network, Beam in reaches the whole network the host is in; the Awacino terminal opens on the host itself.

Updates keep the pairing

Identity, certificates and client updates live in the awacino-data volume, so recreating or updating the container keeps the device paired.

NAS container managers

Synology Container Manager, QNAP Container Station, TrueNAS SCALE and Unraid - paste the compose file and start it.

Many devices

Each device gets its own setup code from the app, so you can roll the same compose file out to many hosts, one code each.

Kubernetes

The image runs wherever Docker, Docker Compose and NAS container managers run. Kubernetes deployment (DaemonSet / Helm) is planned.

Why a container

No packages to install on the host and nothing to configure by hand: the container brings the client, keeps it updated and starts with Docker. No port forwarding, no VPN server.

Questions people ask

How do I get remote access to a Docker host?

Run the Awacino image with docker compose. The host appears in the Awacino app, and you reach it and its network - terminal, SSH, web interfaces - directly and end-to-end encrypted.

Does the container start automatically after a reboot?

Yes. The compose file sets restart: unless-stopped, so it starts with Docker on every boot.

Can I use one setup code for many devices?

No, each device gets its own setup code from the app and uses it once.

Is there a Helm chart for Kubernetes?

Not yet. Kubernetes deployment (DaemonSet / Helm) is planned; today the image runs with Docker, Docker Compose and NAS container managers.

Try two slots for freeSmart terminal