From 2d5adfb4f353c45a1f53b8f0ff403e5fa2aa7629 Mon Sep 17 00:00:00 2001 From: LinuxServer-CI Date: Sat, 13 Jul 2024 17:58:43 +0000 Subject: [PATCH] Bot Updating Templated Files --- .github/workflows/permissions.yml | 2 ++ README.md | 6 ++++++ 2 files changed, 8 insertions(+) diff --git a/.github/workflows/permissions.yml b/.github/workflows/permissions.yml index 1447bc5..02e1bdb 100755 --- a/.github/workflows/permissions.yml +++ b/.github/workflows/permissions.yml @@ -5,6 +5,8 @@ on: - '**/run' - '**/finish' - '**/check' + - 'root/migrations/*' + jobs: permission_check: uses: linuxserver/github-workflows/.github/workflows/init-svc-executable-permissions.yml@v1 diff --git a/README.md b/README.md index a69652f..59458b0 100644 --- a/README.md +++ b/README.md @@ -83,6 +83,11 @@ Use the optional paths if you don't understand, or don't want hardlinks/atomic m The folks over at servarr.com wrote a good [write-up](https://wiki.servarr.com/docker-guide#consistent-and-well-planned-paths) on how to get started with this. +## Read-Only Operation + +This image can be run with a read-only container filesystem. For details please [read the docs](https://docs.linuxserver.io/misc/read-only/). + + ## Usage To help you get started creating a container from this image you can either use docker-compose or the docker cli. @@ -137,6 +142,7 @@ Containers are configured using parameters passed at runtime (such as those abov | `-v /config` | Persistent config files | | `-v /downloads` | Local path for finished downloads. | | `-v /incomplete-downloads` | Local path for incomplete-downloads. | +| `--read-only=true` | Run container with a read-only filesystem. Please [read the docs](https://docs.linuxserver.io/misc/read-only/). | ## Environment variables from files (Docker secrets)