Have you inspected the logs in storage/logs/laravel.log for any errors? Not sure how? This is a docker install with startup issues
Describe the bug
Spinning up a fresh install of the latest docker debian v5.11.41.
Everything looks great in the logs until I start getting an endless loop for app-1:
Public Folder is up to date
In PackageManifest.php line 179:
The /var/www/html/bootstrap/cache directory must be present and writable.
Steps To Reproduce
Download dockerfiles from Git repository
Update .env and docker-compose.yml
start everything with: docker compose up -d && docker compose logs -f
Thank you, sir! That definitely did help my direction, however, in the end I could not get the app container up using local folders instead of volumes.
I’m running rootless Docker.
In the docker-compose.yml I specified local folders for ease of backup like this:
volumes:
- ./.env:/var/www/html/.env
# - ./php/php.ini:/usr/local/etc/php/conf.d/invoiceninja.ini:ro
# - ./php/php-fpm.conf:/usr/local/etc/php-fpm.d/invoiceninja.conf:ro
# - ./supervisor/supervisord.conf:/etc/supervisor/conf.d/supervisord.conf:ro
- ./docker-data/app_cache:/var/www/html/bootstrap/cache
- ./docker-data/app_public:/var/www/html/public
- ./docker-data/app_storage:/var/www/html/storage
Unfortunately, even after trying to set the folders to 777, the best I got was an error that I needed to specify a cache folder.
Most of the fixes I read to create the /var/www/html/bootstrap/cache folder manually and change it’s permissions seem to be referring to local installs… I have zero idea how I’d do that to a docker image. I can’t even exec into it because it keeps failing and restarting.
I then decided to test with the original docker volumes from the repo’s docker-compose.yml and lo and behold it works just fine. So I’m guessing it has to be a permissions issue on the folders but I have no idea what those permissions would have to be as it didn’t even work by chmod-ing them to 777.
Would love some help if anyone has any ideas! Until then I guess I’ll run like it is with the docker volumes and figure out a way to back those up.
