Awacino ZeroTrust Home Network

Awacino in Docker on your network storage

One compose file, and your NAS and home network are reachable from anywhere.

Download the app
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.

Kubernetes: one Helm command per cluster

Awacino runs as a DaemonSet: every selected node becomes its own Beam-in device, with outbound connections only - no Service, no Ingress, no open port.

$ helm install awacino oci://docker.awacino.net/awacino/charts/awacino-unattended -n awacino --create-namespace
$ kubectl label namespace awacino pod-security.kubernetes.io/enforce=privileged

Pair each node. Create one setup code per node in the Awacino app (Add unattended device) and add it with --set-string setupCodes.<node>=<code>. Without Helm, a plain manifest does the same.

Where it runs: Standard Kubernetes clusters, k3s and kind; managed clusters with standard node pools (GKE Standard, EKS managed nodes, AKS); OpenShift with the privileged security context constraint. The pods run privileged on the host network, like any VPN or network agent, so the cluster has to allow privileged containers and host networking - GKE Autopilot, EKS Fargate, AKS virtual nodes and namespaces with strict pod security do not.

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.

Container managers on network storage

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

Several devices

Each device gets its own setup code from the app, so the same compose file works on your NAS, your homelab box and the one at your parents', one code each.

Kubernetes

One Helm command per cluster: Awacino runs as a DaemonSet, and every node becomes its own Beam-in device.

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?

Yes. One Helm command installs Awacino as a DaemonSet; each node is paired with its own setup code and becomes its own Beam-in device. A plain manifest is available as well.