Cloud in a Bottle puts every self-hosted app in its own user namespace by default

Rootless Podman under a single supervising service is a sound way to build this. The isolation claim rests on one detail of the configuration. Per-app user namespaces only close the host hole if each app holds its own subordinate UID and GID range, so that a container root breaking out lands on an unprivileged host account that owns nothing else. If openhost.service runs every container under one shared service account instead, the blast radius is that account. That account holds the catalog. The post says openhost.service manages the lifecycle of rootless Podman containers and that each app runs within its own user namespace ^[3][4]; it does not publish the unit file or the subuid allocation.

The comparison to YunoHost is the dev.to writeup's own assessment. It calls the arrangement "a critical security win" and describes it as mitigating the "one broken app destroys the host" risk found in platforms like YunoHost ^[4]. Anyone who wants that verified has to install both and read their defaults.

The HTTP-only limit on Cloudflare Tunnel is why the post's own remedy comes from a vendor ^[9]. Its two example commands are `ssh -p 443 -R0:localhost:25565 [email protected]` for a raw TCP service and `ssh -p 443 -R0:localhost:8080 free.pinggy.io` for the dashboard on port 8080 ^[10][11]. They differ by the `tcp@` user and the forwarded port, so raw TCP is a separate endpoint mode from the web one ^[17]. The post calls the project documentation's discussion of networking its most honest part, and then names a tunnel provider as the fix ^[16][10].

The `bottle` CLI is aimed at coding agents, letting automation scripts deploy and manage containers without manual credential handling, and the documentation is served in machine-readable form at `/docs/all.md` ^[12][13]. An agent that can call `bottle` can create containers.

Feedback on the project also raised persistent storage as a reason for hesitation ^[15]. The catalog includes Vaultwarden ^[7], so where volumes live, and what happens to them when a container is replaced, is the first thing I would test on a box I intended to keep.