Closed vitis586 closed 7 months ago
Having the exact same issue with my docker container. Web page displaying these Depricated errors. Here are mine in case there are any differences:
Deprecated: Return type of Illuminate\Container\Container::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 1159
Deprecated: Return type of Illuminate\Container\Container::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 1170
Deprecated: Return type of Illuminate\Container\Container::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 1182
Deprecated: Return type of Illuminate\Container\Container::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 1195
Deprecated: Method ReflectionParameter::getClass() is deprecated in /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 788
Deprecated: Method ReflectionParameter::getClass() is deprecated in /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 862
Deprecated: Method ReflectionParameter::getClass() is deprecated in /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 788
Deprecated: Method ReflectionParameter::getClass() is deprecated in /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 862
Deprecated: Return type of Illuminate\Routing\RouteCollection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/RouteCollection.php on line 343
Deprecated: Return type of Illuminate\Routing\RouteCollection::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/RouteCollection.php on line 333
Deprecated: Return type of Illuminate\Http\Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Http/Request.php on line 552
Deprecated: Return type of Illuminate\Http\Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Http/Request.php on line 563
Deprecated: Return type of Illuminate\Http\Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Http/Request.php on line 575
Deprecated: Return type of Illuminate\Http\Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Http/Request.php on line 586
Deprecated: Return type of Symfony\Component\HttpFoundation\ParameterBag::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/http-foundation/ParameterBag.php on line 220
Deprecated: Return type of Symfony\Component\HttpFoundation\ParameterBag::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/http-foundation/ParameterBag.php on line 230
Deprecated: Return type of Symfony\Component\HttpFoundation\HeaderBag::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/http-foundation/HeaderBag.php on line 280
Deprecated: Return type of Symfony\Component\HttpFoundation\HeaderBag::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/http-foundation/HeaderBag.php on line 290
Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /var/www/html/vendor/symfony/http-foundation/Request.php on line 316
Deprecated: mb_strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /var/www/html/vendor/laravel/framework/src/Illuminate/Support/Str.php on line 94
Deprecated: mb_strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /var/www/html/vendor/laravel/framework/src/Illuminate/Support/Str.php on line 94
Deprecated: auto_detect_line_endings is deprecated in /var/www/html/vendor/vlucas/phpdotenv/src/Loader.php on line 167
Deprecated: Return type of Illuminate\Config\Repository::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Config/Repository.php on line 116
Deprecated: Return type of Illuminate\Config\Repository::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Config/Repository.php on line 127
Deprecated: Return type of Illuminate\Config\Repository::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Config/Repository.php on line 139
Deprecated: Return type of Illuminate\Config\Repository::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Config/Repository.php on line 150
Deprecated: Return type of Symfony\Component\Finder\Finder::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/finder/Finder.php on line 565
Deprecated: Return type of Symfony\Component\Finder\Finder::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/finder/Finder.php on line 636
Deprecated: Return type of Symfony\Component\Finder\Iterator\FilterIterator::rewind() should either be compatible with FilterIterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/finder/Iterator/FilterIterator.php on line 32
Deprecated: Return type of Symfony\Component\Finder\Iterator\FileTypeFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/finder/Iterator/FileTypeFilterIterator.php on line 42
Deprecated: Return type of Symfony\Component\Finder\Iterator\RecursiveDirectoryIterator::getChildren() should either be compatible with RecursiveDirectoryIterator::getChildren(): RecursiveDirectoryIterator, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/finder/Iterator/RecursiveDirectoryIterator.php on line 85
Deprecated: Return type of Symfony\Component\Finder\Iterator\RecursiveDirectoryIterator::rewind() should either be compatible with FilesystemIterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/finder/Iterator/RecursiveDirectoryIterator.php on line 113
Deprecated: Return type of Symfony\Component\Finder\Iterator\RecursiveDirectoryIterator::current() should either be compatible with FilesystemIterator::current(): SplFileInfo|FilesystemIterator|string, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/finder/Iterator/RecursiveDirectoryIterator.php on line 65
Deprecated: Return type of Symfony\Component\Finder\Iterator\ExcludeDirectoryFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/finder/Iterator/ExcludeDirectoryFilterIterator.php on line 55
Deprecated: Return type of Symfony\Component\Finder\Iterator\ExcludeDirectoryFilterIterator::hasChildren() should either be compatible with RecursiveIterator::hasChildren(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/finder/Iterator/ExcludeDirectoryFilterIterator.php on line 71
Deprecated: Return type of Symfony\Component\Finder\Iterator\ExcludeDirectoryFilterIterator::getChildren() should either be compatible with RecursiveIterator::getChildren(): ?RecursiveIterator, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/finder/Iterator/ExcludeDirectoryFilterIterator.php on line 76
Deprecated: Return type of Symfony\Component\Finder\Iterator\FilterIterator::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/finder/Iterator/FilterIterator.php on line 32
Deprecated: Return type of Symfony\Component\Finder\Iterator\FilenameFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/finder/Iterator/FilenameFilterIterator.php on line 28
Deprecated: Return type of Symfony\Component\Finder\Iterator\PathFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/symfony/finder/Iterator/PathFilterIterator.php on line 27
Deprecated: Return type of Illuminate\Database\Eloquent\Model::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php on line 1300
Deprecated: Return type of Illuminate\Database\Eloquent\Model::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php on line 1311
Deprecated: Return type of Illuminate\Database\Eloquent\Model::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php on line 1323
Deprecated: Return type of Illuminate\Database\Eloquent\Model::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php on line 1334
Deprecated: Return type of Illuminate\Database\Eloquent\Model::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php on line 927
I just tried wiping my testing instance and starting over. Still not working the only difference being that the errors end up in the container logs.
The docker container got an update during today but that one is still not working.
I just went back to 3.0.15 and it's good again. Just going to wait until they figure out what's wrong with it.
On Tue, Aug 22, 2023 at 1:20 PM vitis586 @.***> wrote:
I just tried wiping my testing instance and starting over. Still not working the only difference being that the errors end up in the container logs.
The docker container got an update during today but that one is still not working.
— Reply to this email directly, view it on GitHub https://github.com/akaunting/docker/issues/95#issuecomment-1688614116, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7VJLV2LQDF4LIGXQIWKV3XWTS57ANCNFSM6AAAAAA3ZSDK4M . You are receiving this because you commented.Message ID: @.***>
Spoke too soon I guess the database got upgraded and rolling back means I can't create any invoices or bills etc.
On Tue., Aug. 22, 2023, 9:00 p.m. Rob M, @.***> wrote:
I just went back to 3.0.15 and it's good again. Just going to wait until they figure out what's wrong with it.
On Tue, Aug 22, 2023 at 1:20 PM vitis586 @.***> wrote:
I just tried wiping my testing instance and starting over. Still not working the only difference being that the errors end up in the container logs.
The docker container got an update during today but that one is still not working.
— Reply to this email directly, view it on GitHub https://github.com/akaunting/docker/issues/95#issuecomment-1688614116, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7VJLV2LQDF4LIGXQIWKV3XWTS57ANCNFSM6AAAAAA3ZSDK4M . You are receiving this because you commented.Message ID: @.***>
Noticed that the latest image was updated 2 hours ago but still no go...getting the deprication errors. I really hope this gets resolved soon, I'm dead in the water because when it upgraded it also updated the database and now I can't roll back.
On Fri., Aug. 25, 2023, 8:46 a.m. Rob M, @.***> wrote:
Spoke too soon I guess the database got upgraded and rolling back means I can't create any invoices or bills etc.
On Tue., Aug. 22, 2023, 9:00 p.m. Rob M, @.***> wrote:
I just went back to 3.0.15 and it's good again. Just going to wait until they figure out what's wrong with it.
On Tue, Aug 22, 2023 at 1:20 PM vitis586 @.***> wrote:
I just tried wiping my testing instance and starting over. Still not working the only difference being that the errors end up in the container logs.
The docker container got an update during today but that one is still not working.
— Reply to this email directly, view it on GitHub https://github.com/akaunting/docker/issues/95#issuecomment-1688614116, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7VJLV2LQDF4LIGXQIWKV3XWTS57ANCNFSM6AAAAAA3ZSDK4M . You are receiving this because you commented.Message ID: @.***>
I also tried most of the new builds but without luck. It is strange that the image gets updated but it is still 3.0.16. Seems like that some of the accompanying packages are getting updates.
I am using only the transactions part so far and that is working.
It is also strange that it is just two of us having issues.
I managed to get it working by rolling back to 3.0.13. Haven't tried moving beyond but might test each version to see.
On Fri., Aug. 25, 2023, 2:33 p.m. vitis586, @.***> wrote:
I also tried most of the new builds but without luck. It is strange that the image gets updated but it is still 3.0.16. Seems like that some of the accompanying packages are getting updates.
I am using only the transactions part so far and that is working.
— Reply to this email directly, view it on GitHub https://github.com/akaunting/docker/issues/95#issuecomment-1693776511, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7VJLRUFLUTGIAOPJIOKM3XXDVV5ANCNFSM6AAAAAA3ZSDK4M . You are receiving this because you commented.Message ID: @.***>
I managed to start the test container with the new 3.0.17 via the :latest
tag. The :latest
is currently the same as 3.0.17
tag but there is also 3.0.17-v
with different digest. There are small difference in the dockerfiles. I am not sure if the tag will be getting the updates in the same manor (changing digest while keeping the same tag) or something chnaged. I will not go with :latest
but I will monitor how the updates affect the two 3.0.17 tags a choose one of those probably.
Nor the 3.0.16-v
neither the 3.0.16
are working for me. I have not tried the fpm or alpine versions. I never got those running. They have exposed different port and are not aligned with the documentation.
I will also have a look into Bigcapital as I am not heavily invested in Akaunting yet.
@raenrfm Just to let you know what I sorted out. I am using the latest 3.0.17 but both the 3.0.17
and 3.0.17-v
tags are still changing. I resorted to using the digest as my tag, so I am using tag akaunting/akaunting@sha256:f35f4f77927945a3b7618675d7129be30cd15170e81cfbbc77280651b32affca
. This gives me the latest version but does not get change every now and then. It is locked to the current state of the tag so automatic updates wont work unfortunately. This digest is from last week so it is not the current one.
Ah great work, it's also working for me now, thank you!
On Tue, Sep 12, 2023 at 1:35 PM vitis586 @.***> wrote:
@raenrfm https://github.com/raenrfm Just to let you know what I sorted out. I am using the latest 3.0.17 but both the 3.0.17 and 3.0.17-v tags are still changing. I resorted to using the digest as my tag, so I am using tag @.*** :f35f4f77927945a3b7618675d7129be30cd15170e81cfbbc77280651b32affca. This gives me the latest version but does not get change every now and then. It is locked to the current state of the tag so automatic updates wont work unfortunately.
— Reply to this email directly, view it on GitHub https://github.com/akaunting/docker/issues/95#issuecomment-1716153027, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7VJLUQJ3QJFTX7IHCOEATX2CMNXANCNFSM6AAAAAA3ZSDK4M . You are receiving this because you were mentioned.Message ID: @.***>
So my wife decided to run updates inside our installation and now it's messed up it probably updated something in the database and if I try to recreate the container with the old image I'm getting this now:
components.layouts.error.head components.layouts.error.content components.layouts.error.scripts
and nothing else. I tried the latest image and it goes through setup but never connects to my mariadb...it's stuck on step 2...any ideas?
On Tue, Sep 12, 2023 at 1:35 PM vitis586 @.***> wrote:
@raenrfm https://github.com/raenrfm Just to let you know what I sorted out. I am using the latest 3.0.17 but both the 3.0.17 and 3.0.17-v tags are still changing. I resorted to using the digest as my tag, so I am using tag @.*** :f35f4f77927945a3b7618675d7129be30cd15170e81cfbbc77280651b32affca. This gives me the latest version but does not get change every now and then. It is locked to the current state of the tag so automatic updates wont work unfortunately.
— Reply to this email directly, view it on GitHub https://github.com/akaunting/docker/issues/95#issuecomment-1716153027, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7VJLUQJ3QJFTX7IHCOEATX2CMNXANCNFSM6AAAAAA3ZSDK4M . You are receiving this because you were mentioned.Message ID: @.***>
Hi @raenrfm, there has not been any database migration since the 3.1.0 so the database should be fine. I would back up the database and try to update the image. I use or used these tags:
For future I suggest using automated database backup. I use this https://hub.docker.com/r/tiredofit/db-backup/
Is the failing installation maybe failing because of the latest changes, that detect if the service is already installed? I also noticed that while changing to 3.1.5. See more and potential fix for you in - https://github.com/akaunting/docker/issues/107
Hi, My testing container only works locally, is not exposed to internet and uses
:latest
tag. My production is exposed to the internet and uses:3
tag. Everything was working fine up until today. I filled my production container with some data yesterday evening. I went through the data see all of it. Today both of containers are showing the error in the browser. The docker tags got updated yesterday so I guess it has to be something connected with this.Logs for the container do not show anything useful. There are HTTP 200s on every access but I still see only the error below.