Match upstream Flood runtime while keeping torrent service separate
This commit is contained in:
1 parent
cb32b760a5
commit
8b6742f484
3 files changed
+10
-6
No files matched your search
@@ -24,8 +24,12 @@ runner image store, and the temporary builder and cache are removed afterward.
|
||||
No image archives or build records are uploaded to Gitea, and no local container
|
||||
builds are required.
|
||||
|
||||
Base image: Node.js 24 on Alpine Linux 3.24 stable (`node:24-alpine3.24`),
|
||||
including the latest patch updates in those release series.
|
||||
Base image: Node.js 24.18.1 on Alpine Linux 3.24 stable (`node:24.18.1-alpine3.24`),
|
||||
with the Alpine stable series explicitly selected.
|
||||
|
||||
The image build starts the actual Flood server and requires HTTP 200 before
|
||||
publishing; it does not start a torrent daemon.
|
||||
|
||||
The entrypoint uses `npm run start`, matching upstream v4.16.2, while retaining
|
||||
`--host=0.0.0.0` and `--rundir=/server/`. The upstream combined rTorrent stage
|
||||
is deliberately excluded.
|
||||
Reference in new issue
Block a user