Awacino ZeroTrust Company Network

Docker and Kubernetes

A ready Docker image with one compose file per host, and one Helm command per Kubernetes cluster.

Docker

One compose file per host

Image: docker.awacino.net/awacino/unattended:latest for linux/amd64 and linux/arm64. In the app, choose Add unattended device → Install on NAS: it shows a one-time setup code and a compose file with the code filled in.

docker compose up -d

The device appears in the app within a minute. restart: unless-stopped brings it back with Docker after every reboot. Identity, certificates and client updates live in the awacino-data volume, so recreating or updating the container keeps the device paired.

Kubernetes

One Helm command per cluster

Awacino runs as a DaemonSet: every selected node of the cluster becomes its own Beam-in device. You reach the node's network, route through it and open a terminal on the node - 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. Every node is its own device with its own setup code: list the nodes with kubectl get nodes, create one setup code per node in the Awacino app (Add unattended device), then run helm upgrade awacino oci://docker.awacino.net/awacino/charts/awacino-unattended -n awacino --reuse-values --set-string setupCodes.<node>=<code>. Each node appears in the app within a minute.

Without Helm: a plain manifest, awacino-unattended.yaml, 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.

At scale

Many hosts, one file

One code per host

Each device gets its own setup code from the app and uses it once; the compose file stays the same.

The host's network

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

Nothing on the host

No packages to install and nothing to configure by hand: the container brings the client and keeps it updated.

Run Awacino where your containers run

Docker, Docker Compose and NAS container managers.