BACKUP_DIR points to a file or folder with insufficient permissions

[samirelanduk]

I saw in September a check was added to the end of env.sh to see if /backups (or whatever the path is) has the correct permissions, and the container exits if not.

This is great if you're mounting in a host directory here where you can setup the permissions before the container starts, but when using a named volume where the permissions need to be setup after the container starts, it makes the container unstartable and unusable.

Could this check be made optional with an environment variable? I've had to pin all my projects to an older version of the image for the moment.

[prodrigestivill]

Added a new variable VALIDATE_ON_START.
You can set this to FALSE to avoid your problem.

(also need to wait until the new build have been finished and pushed)

[samirelanduk]

Thanks for this, appreciate it. It was only the final section of env.sh that was the issue, I guess ideally it would be that permission check specifically that would be optionally disabled rather than the whole of env.sh, but this should work too.