Shipped quadlets reference a volume unit that does not exist #37

New issue

Closed

opened 2026-10-17 05:23:13 +00:00 by agent-pi · 1 comment

agent-pi commented

2026-10-17 05:23:13 +00:00

Collaborator

Bringing the pod up from deploy/ fails at quadlet conversion:

converting "xique-worker.container": requested Quadlet source xique-imports-volume.volume was not found
converting "xique-web.container": requested Quadlet source xique-imports-volume.volume was not found

Both xique-web.container and xique-worker.container declare Volume=xique-imports-volume.volume:/data/imports-temp, but the shipped volume unit is named xique-imports.volume. Quadlet resolves these sources by literal filename, so the documented install (cp deploy/... ~/.config/containers/systemd/) cannot work as written. The podman volume name itself is unaffected — the volume unit pins it with VolumeName=xique-imports-volume.

Bringing the pod up from `deploy/` fails at quadlet conversion: ``` converting "xique-worker.container": requested Quadlet source xique-imports-volume.volume was not found converting "xique-web.container": requested Quadlet source xique-imports-volume.volume was not found ``` Both `xique-web.container` and `xique-worker.container` declare `Volume=xique-imports-volume.volume:/data/imports-temp`, but the shipped volume unit is named `xique-imports.volume`. Quadlet resolves these sources by literal filename, so the documented install (`cp deploy/... ~/.config/containers/systemd/`) cannot work as written. The podman volume name itself is unaffected — the volume unit pins it with `VolumeName=xique-imports-volume`.

agent-pi added the

Kind/Bug

Priority

High

labels

2026-10-17 05:23:13 +00:00

agent-pi commented

2026-10-17 05:23:13 +00:00

Author

Collaborator

Plan of attack:

Point the two Volume= references at the shipped filename: Volume=xique-imports.volume:/data/imports-temp in xique-web.container and xique-worker.container. The generated podman volume name stays xique-imports-volume (the volume unit's explicit VolumeName=), and the documented cp deploy/xique-imports.volume ... steps in the README and docs stay true as written.
This is the minimal-churn direction: renaming the file would touch four places (two references + two docs cp commands) for the same result.
Verified by reference-vs-filename consistency across deploy/ (the podman generator resolves Volume=*.volume sources by filename in the quadlet directories, which the reported error itself confirms); the operator's dry run is the live check.

Branch: fix/issue-37-quadlet-volume-filename

Commits:

:bug: fix: point quadlet volume references at the shipped volume unit

PR: POST /repos/marvin8/xique/pulls (head fix/issue-37-quadlet-volume-filename, base main, Closes #N).

Plan of attack: - Point the two `Volume=` references at the shipped filename: `Volume=xique-imports.volume:/data/imports-temp` in `xique-web.container` and `xique-worker.container`. The generated podman volume name stays `xique-imports-volume` (the volume unit's explicit `VolumeName=`), and the documented `cp deploy/xique-imports.volume ...` steps in the README and docs stay true as written. - This is the minimal-churn direction: renaming the file would touch four places (two references + two docs cp commands) for the same result. - Verified by reference-vs-filename consistency across `deploy/` (the podman generator resolves `Volume=*.volume` sources by filename in the quadlet directories, which the reported error itself confirms); the operator's dry run is the live check. Branch: `fix/issue-37-quadlet-volume-filename` Commits: - `:bug: fix: point quadlet volume references at the shipped volume unit` PR: `POST /repos/marvin8/xique/pulls` (head `fix/issue-37-quadlet-volume-filename`, base `main`, `Closes #N`).

agent-pi referenced this issue from a pull request that will close it,

2026-10-17 05:24:03 +00:00

Point quadlet volume references at the shipped volume unit #38

agent-pi closed this issue

2026-10-17 05:32:27 +00:00

agent-pi referenced this issue

2026-10-17 05:47:02 +00:00

Tailscale sidecar points TS_SERVE_CONFIG at a file that is never mounted #39

agent-pi referenced this issue

2026-10-17 05:48:15 +00:00

Point the tailscale sidecar at the mounted serve config #40