From 687775c595aea8f91eaf6c378609c99904079799 Mon Sep 17 00:00:00 2001 From: "Dustin C. Hatch" Date: Tue, 2 Sep 2025 12:21:58 -0500 Subject: [PATCH] invoice-ninja: Fix error in cron container The "cron" container has not been working correctly for some time. No background tasks are getting run, and this error is printed in the log every minute: > `Target class [db.schema] does not exist` It turns out, this is because of the way the PHP `artisan` tool works. It MUST be able to write to the code directory, apparently to build some kind of cache. There may be a way to cache the data ahead of time, but I haven't found it yet. For now, it seems the only way to make Laravel-based applications run in a container is to make the container filesystem mutable. --- invoice-ninja/invoice-ninja.yaml | 2 -- 1 file changed, 2 deletions(-) diff --git a/invoice-ninja/invoice-ninja.yaml b/invoice-ninja/invoice-ninja.yaml index 58eb31d..1e290bd 100644 --- a/invoice-ninja/invoice-ninja.yaml +++ b/invoice-ninja/invoice-ninja.yaml @@ -154,8 +154,6 @@ spec: while sleep 60; do php artisan schedule:run; done env: *env envFrom: *envFrom - securityContext: - readOnlyRootFilesystem: true volumeMounts: *mounts enableServiceLinks: false affinity: