Build Unraid image without Compose labels
This commit is contained in:
@@ -1523,10 +1523,11 @@ Expected Unraid behavior:
|
||||
|
||||
Changed:
|
||||
- Added `deploy/unraid/run-dockerman-container.sh` as the single source of truth for the final Unraid container launch.
|
||||
- Updated Tower deploy scripts so repository deploys build the image with Compose but start the final container with `docker run` and DockerMan labels.
|
||||
- Updated Tower deploy scripts so repository deploys validate the Compose reference, build the image with plain `docker build` and start the final container with `docker run` plus DockerMan labels.
|
||||
- The launch script installs the DockerMan template/icon, removes old `geointel` containers, preserves/migrates the old Compose PostGIS volume when needed and starts the final `geointel` container as DockerMan-managed.
|
||||
- Updated live migration smoke to support direct container execution through `LIVE_SMOKE_CONTAINER=geointel`.
|
||||
|
||||
Expected Unraid behavior:
|
||||
- A deploy from the repo should no longer leave the final app as a plain Compose-owned container.
|
||||
- The final image/container should avoid Compose metadata labels that can confuse Unraid's Docker page.
|
||||
- The running `geointel` container should expose `net.unraid.docker.managed=dockerman`, web UI metadata and icon metadata immediately after deploy.
|
||||
|
||||
Reference in New Issue
Block a user