Deploy Hermes Agent LXC (#118) on gihyeon + IaC hygiene #1

Merged
gihyeon merged 11 commits from hermes-agent-lxc into main 2026-06-19 11:04:17 +09:00
Showing only changes of commit d083d462cf - Show all commits

View File

@@ -1,9 +1,14 @@
# Download Debian 12 LXC template to gihyeon (node1). # Download Debian 12 LXC template to gihyeon (node1).
# overwrite_unmanaged: the template already exists in node1's `local` datastore
# from an earlier run but is not yet tracked in Terraform state. Without this,
# bpg refuses to touch the pre-existing file ("refusing to override existing
# file"). Setting it true lets Terraform adopt/re-download it under management.
resource "proxmox_virtual_environment_download_file" "debian12_template_gihyeon" { resource "proxmox_virtual_environment_download_file" "debian12_template_gihyeon" {
content_type = "vztmpl" content_type = "vztmpl"
datastore_id = "local" datastore_id = "local"
node_name = var.hermes_node node_name = var.hermes_node
url = "http://download.proxmox.com/images/system/debian-12-standard_12.12-1_amd64.tar.zst" url = "http://download.proxmox.com/images/system/debian-12-standard_12.12-1_amd64.tar.zst"
overwrite_unmanaged = true
} }
# Hermes Agent LXC. # Hermes Agent LXC.
@@ -22,9 +27,20 @@ resource "proxmox_virtual_environment_container" "hermes" {
unprivileged = true unprivileged = true
tags = ["ai", "agent", "terraform"] tags = ["ai", "agent", "terraform"]
# Only `nesting` can be set with an API token. Proxmox rejects other feature
# flags from tokens: "changing feature flags (except nesting) is only allowed
# for root@pam". keyctl (if Docker needs it), fuse, and bind mounts are
# applied out-of-band on the node console as root@pam.
features { features {
nesting = true nesting = true
keyctl = true }
# keyctl and bind mounts (mp0/mp1) are applied out-of-band on the node console
# as root@pam (the API token cannot set them — see the features note above).
# Ignore drift on these so a routine `terraform apply` does not try to strip
# the console-applied settings (which would fail without root@pam anyway).
lifecycle {
ignore_changes = [features, mount_point]
} }
operating_system { operating_system {