You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I stumbled upon this issue when creating an automad deployment in my k8s cluster using longhorn as a storage backend with ext4 as it's default fsType.
There are several ways for me to work around this issue, but I think this should be fixed in this image, if possible.
Initially, the container will run /init.sh, which already checks whether or not a folder exists named /app/automad.
When using a new ext4 volume mounted at /app, there will be a lost+found folder
Hey there!
I stumbled upon this issue when creating an automad deployment in my k8s cluster using longhorn as a storage backend with ext4 as it's default fsType.
There are several ways for me to work around this issue, but I think this should be fixed in this image, if possible.
Initially, the container will run
/init.sh
, which already checks whether or not a folder exists named /app/automad.When using a new ext4 volume mounted at /app, there will be a lost+found folder
The Composer Script doesn't seem to like that:
From what I can find on the internet, composer itself doesn't really have an option to work around this behaviour.
The text was updated successfully, but these errors were encountered: