forked from heavy-duty/box
aad576a86a
box setup-host stopped halfway when it had to add you to incus-admin: it usermod'd, printed a NOTE telling you to re-login and re-run, and exited 0 — a success-shaped no-op with no boxnet, no ACL, no box-net profile and no firewall behind it. It now re-execs itself under 'sg incus-admin' and finishes in that same invocation. The membership check was also asking the wrong question. 'id -nG "$USER"' names a user, so it reads the group database — which lists incus-admin the instant usermod returns, while the shell's own credentials still lack it (supplementary groups are fixed at login). A same-session re-run therefore passed the check and died further down on a bare permission error from incus that mentioned neither the group nor the re-login. Argless 'id -nG' asks the process what it actually holds, which is what incus checks when it opens /var/lib/incus/unix.socket. With one run now sufficient, install.sh runs the setup itself instead of printing a warning and leaving the user a command: the install reported success and 'box new' then failed on a host with no Incus. setup-host is idempotent, so doing this on every install is also how an upgraded host picks up stack changes. BOX_SKIP_SETUP_HOST=1 opts out, and a failed setup leaves the install standing and says what to re-run. Fixes #63 Fixes #64 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| box-firewall.service | ||
| box-firewall.sh | ||
| migrate-host.sh | ||
| setup-host.sh | ||
| teardown-host.sh | ||