Open nithrous opened 1 year ago
Also tried a solution from here: https://akaunting.com/forum/discussion/general/laravel-deprication-errors-docker-container
UPDATE: with image version 3.0.15 it works again.
The solution is to use fixed image verison in your docker-compose.yml "image: akaunting/akaunting:3.0.15" until the latest image will be fixed.
But get
E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
Do you know how to fix it?
I do not recall if I run the v3.0.15 but I had similar issues with v3.0.16. The later version was working and it broke over night even though I was locked to it. The thing is that the images are changing almost every day, so locking to a version tag is not enough. You have to lock to specific digest. One of the users had to rollback to v3.0.13 to get everything working so that might also be worth trying. More information in here https://github.com/akaunting/docker/issues/95 BTW yesterday I managed to finally run the latest 3.1 version which was not working for quite some time again (PHP errors). I even managed to fulfill the requirements for the number of users but any change that requires database throws errors so I might be migrating back to 3.0.17 today.
Os: Ubuntu 18
Hi, went through installation steps, but did not made any changes in environments, just set 12600 port in docker-compose.yml. Two containers appeared: akaunting and akaunting-db
When I open an app using
{ip_address}:12600
I see such output:How to fix it?