Closed ShlomiD83 closed 1 year ago
@ShlomiD83 can you please dump some logs below so I can take a look?
@alexjustesen the issue is that the logs for the container are blank. I just tried to spin up a container after seeing the video from DBTech and I get the same "error" in the logs. I am running this in portainer on an Ubuntu 20.04 VM with 8 cores and 16GB RAM. The only thing that I have changed from the compose example is the volume and the port (as well).
I have been looking forward to an updated version of what I have enjoyed. Keep up the great work and I will keep testing for you.
Interesting, probably a good opportunity to update the docs and provide a dedicated Portainer install section. It's also possible there aren't any logs yet for the container in your instance as I can see logging happening on my deployment.
I am following the example here: https://docs.speedtest-tracker.dev/getting-started/installation - Docker (MariaDB/MySQL)
I did see the example on github and not sure why they are different but that is the one that was covered on DBTech's video.
I did see the example on github and not sure why they are different but that is the one that was covered on DBTech's video.
can you drop a link to that example in case I missed an old doc?
@ShlomiD83 can you please dump some logs below so I can take a look?
which logs? It seems to be empty. I get "ERR_CONNECTION_REFUSED" when connecting to the web UI.
I am receiving the same error above "No log line matching the '' filter". Eventually the logs start generating. Below is my logs:
[previous exception] [object] (PDOException(code: 0): PDO::__construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known at /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php:70) [stacktrace]
"} In Connection.php line 760:
SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for db failed:
Name or service not known (SQL: select * from information_schema.tables wh
ere table_schema = speedtest_tracker and tablename = migrations and table
type = 'BASE TABLE')
In Connector.php line 70:
SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for db failed:
Name or service not known
In Connector.php line 70:
PDO::__construct(): php_network_getaddresses: getaddrinfo for db failed: Na
me or service not known
s6-rc: warning: unable to start service startup: command exited 1 ❌ There seems to be a failure in checking the web server + PHP-FPM. Here's the response: 127.0.0.1 - - [02/Nov/2022:21:25:55 +0000] "GET /ping HTTP/1.1" 301 162 "-" "curl/7.81.0" /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. prog: fatal: stopping the container. [02-Nov-2022 21:25:55] NOTICE: Terminating ... [02-Nov-2022 21:25:55] NOTICE: exiting, bye-bye!
I am receiving the same error above "No log line matching the '' filter". Eventually the logs start generating. Below is my logs: #0 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(70): PDO->construct() #1 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(100): Illuminate\Database\Connectors\Connector->createPdoConnection() #2 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(50): Illuminate\Database\Connectors\Connector->tryAgainIfCausedByLostConnection() #3 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/MySqlConnector.php(24): Illuminate\Database\Connectors\Connector->createConnection() #4 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/ConnectionFactory.php(184): Illuminate\Database\Connectors\MySqlConnector->connect() #5 [internal function]: Illuminate\Database\Connectors\ConnectionFactory->Illuminate\Database\Connectors{closure}() #6 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(1171): call_user_func() #7 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(1207): Illuminate\Database\Connection->getPdo() #8 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(486): Illuminate\Database\Connection->getReadPdo() #9 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(414): Illuminate\Database\Connection->getPdoForSelect() #10 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(753): Illuminate\Database\Connection->Illuminate\Database{closure}() #11 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(899): Illuminate\Database\Connection->runQueryCallback() #12 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(879): Illuminate\Database\Connection->tryAgainIfCausedByLostConnection() #13 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(723): Illuminate\Database\Connection->handleQueryException() #14 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(422): Illuminate\Database\Connection->run() #15 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Schema/MySqlBuilder.php(44): Illuminate\Database\Connection->select() #16 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/DatabaseMigrationRepository.php(169): Illuminate\Database\Schema\MySqlBuilder->hasTable() #17 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(683): Illuminate\Database\Migrations\DatabaseMigrationRepository->repositoryExists() #18 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(138): Illuminate\Database\Migrations\Migrator->repositoryExists() #19 /var/www/html/vendor/laravel/framework/src/Illuminate/Support/helpers.php(247): Illuminate\Database\Console\Migrations\MigrateCommand->Illuminate\Database\Console\Migrations{closure}() #20 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(157): retry() #21 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(114): Illuminate\Database\Console\Migrations\MigrateCommand->repositoryExists() #22 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(82): Illuminate\Database\Console\Migrations\MigrateCommand->prepareDatabase() #23 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(616): Illuminate\Database\Console\Migrations\MigrateCommand->Illuminate\Database\Console\Migrations{closure}() #24 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(102): Illuminate\Database\Migrations\Migrator->usingConnection() #25 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): Illuminate\Database\Console\Migrations\MigrateCommand->handle() #26 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Util.php(41): Illuminate\Container\BoundMethod::Illuminate\Container{closure}() #27 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\Container\Util::unwrapIfClosure() #28 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(37): Illuminate\Container\BoundMethod::callBoundMethod() #29 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(651): Illuminate\Container\BoundMethod::call() #30 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Command.php(178): Illuminate\Container\Container->call() #31 /var/www/html/vendor/symfony/console/Command/Command.php(308): Illuminate\Console\Command->execute() #32 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Command.php(148): Symfony\Component\Console\Command\Command->run() #33 /var/www/html/vendor/symfony/console/Application.php(1014): Illuminate\Console\Command->run() #34 /var/www/html/vendor/symfony/console/Application.php(301): Symfony\Component\Console\Application->doRunCommand() #35 /var/www/html/vendor/symfony/console/Application.php(171): Symfony\Component\Console\Application->doRun() #36 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Application.php(102): Symfony\Component\Console\Application->run() #37 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(155): Illuminate\Console\Application->run() #38 /var/www/html/artisan(37): Illuminate\Foundation\Console\Kernel->handle() #39 {main} [previous exception] [object] (PDOException(code: 0): PDO::construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known at /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php:70) � [stacktrace] #0 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(70): PDO->__construct() #1 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(100): Illuminate\Database\Connectors\Connector->createPdoConnection() #2 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(50): Illuminate\Database\Connectors\Connector->tryAgainIfCausedByLostConnection() #3 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/MySqlConnector.php(24): Illuminate\Database\Connectors\Connector->createConnection() #4 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/ConnectionFactory.php(184): Illuminate\Database\Connectors\MySqlConnector->connect() #5 [internal function]: Illuminate\Database\Connectors\ConnectionFactory->Illuminate\Database\Connectors{closure}() #6 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(1171): call_user_func() #7 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(1207): Illuminate\Database\Connection->getPdo() #8 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(486): Illuminate\Database\Connection->getReadPdo() #9 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(414): Illuminate\Database\Connection->getPdoForSelect() #10 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(753): Illuminate\Database\Connection->Illuminate\Database{closure}() #11 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(899): Illuminate\Database\Connection->runQueryCallback() #12 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(879): Illuminate\Database\Connection->tryAgainIfCausedByLostConnection() #13 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(723): Illuminate\Database\Connection->handleQueryException() #14 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(422): Illuminate\Database\Connection->run() #15 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Schema/MySqlBuilder.php(44): Illuminate\Database\Connection->select() #16 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/DatabaseMigrationRepository.php(169): Illuminate\Database\Schema\MySqlBuilder->hasTable() #17 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(683): Illuminate\Database\Migrations\DatabaseMigrationRepository->repositoryExists() #18 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(138): Illuminate\Database\Migrations\Migrator->repositoryExists() #19 /var/www/html/vendor/laravel/framework/src/Illuminate/Support/helpers.php(247): Illuminate\Database\Console\Migrations\MigrateCommand->Illuminate\Database\Console\Migrations{closure}() #20 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(157): retry() #21 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(114): Illuminate\Database\Console\Migrations\MigrateCommand->repositoryExists() #22 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(82): Illuminate\Database\Console\Migrations\MigrateCommand->prepareDatabase() #23 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(616): Illuminate\Database\Console\Migrations\MigrateCommand->Illuminate\Database\Console\Migrations{closure}() #24 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(102): Illuminate\Database\Migrations\Migrator->usingConnection() #25 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): Illuminate\Database\Console\Migrations\MigrateCommand->handle() #26 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Util.php(41): Illuminate\Container\BoundMethod::Illuminate\Container{closure}() #27 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\Container\Util::unwrapIfClosure() #28 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(37): Illuminate\Container\BoundMethod::callBoundMethod() #29 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(651): Illuminate\Container\BoundMethod::call() #30 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Command.php(178): Illuminate\Container\Container->call() #31 /var/www/html/vendor/symfony/console/Command/Command.php(308): Illuminate\Console\Command->execute() #32 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Command.php(148): Symfony\Component\Console\Command\Command->run() #33 /var/www/html/vendor/symfony/console/Application.php(1014): Illuminate\Console\Command->run() #34 /var/www/html/vendor/symfony/console/Application.php(301): Symfony\Component\Console\Application->doRunCommand() #35 /var/www/html/vendor/symfony/console/Application.php(171): Symfony\Component\Console\Application->doRun() #36 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Application.php(102): Symfony\Component\Console\Application->run() #37 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(155): Illuminate\Console\Application->run() #38 /var/www/html/artisan(37): Illuminate\Foundation\Console\Kernel->handle() #39 {main} "} In Connection.php line 760:
SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for db failed: Name or service not known (SQL: select * from information_schema.tables wh ere table_schema = speedtest_tracker and tablename = migrations and table type = 'BASE TABLE')
In Connector.php line 70:
SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for db failed: Name or service not known
In Connector.php line 70:
PDO::__construct(): php_network_getaddresses: getaddrinfo for db failed: Na me or service not known
s6-rc: warning: unable to start service startup: command exited 1 ❌ There seems to be a failure in checking the web server + PHP-FPM. Here's the response: 127.0.0.1 - - [02/Nov/2022:21:25:55 +0000] "GET /ping HTTP/1.1" 301 162 "-" "curl/7.81.0" /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. prog: fatal: stopping the container. [02-Nov-2022 21:25:55] NOTICE: Terminating ... [02-Nov-2022 21:25:55] NOTICE: exiting, bye-bye!
I've waited a few minutes and the logs started filling up too. now the container is working and the web UI is accessible.
the container takes forever to load up after restart/recreate. why is that?
Are you sure you're using mine? Most start times are between 2 and 6s unless it's the first start when it creates a database for you.
Are you sure you're using mine? Most start times are between 2 and 6s unless it's the first start when it creates a database for you.
'ghcr.io/alexjustesen/speedtest-tracker:latest'
That's the image I'm using, it's seems to be yours..
the container takes forever to load up after restart/recreate.
never saw this happening here. pretty quick actually.
the container takes forever to load up after restart/recreate.
never saw this happening here. pretty quick actually.
I've timed it at 8 minutes to load up.
I've timed it at 8 minutes to load up.
Houston, you have a problem...
I've timed it at 8 minutes to load up.
Houston, you have a problem...
That's the only container that's acting up. I'm running another 21 containers without any issues and loading times.
Can you give me some details on your platform you're deploying on along with if you're using sqlite or another db?
I've timed it at 8 minutes to load up.
Houston, you have a problem...
That's the only container that's acting up. I'm running another 21 containers without any issues and loading times.
I'm running 66 containers...never took 8 minutes for one of them, and I have pretty "heavy" containers too. Take also into account you're the only one reporting this problem.
What platform are you on? Can you try an older version tag too, just to verify.
Can you give me some details on your platform you're deploying on along with if you're using sqlite or another db?
Raspberry pi 4 8GB, using sqlite. Plain docker via Portainer.
I've timed it at 8 minutes to load up.
Houston, you have a problem...
That's the only container that's acting up. I'm running another 21 containers without any issues and loading times.
I'm running 66 containers...never took 8 minutes for one of them, and I have pretty "heavy" containers too. Take also into account you're the only one reporting this problem.
What platform are you on? Can you try an older version tag too, just to verify.
tried with "ghcr.io/alexjustesen/speedtest-tracker:v.0.1.0-beta". same behavior.
are you on sdcard?
if you have mysql/mariadb, can you create the db and try with that configuration?
are you on sdcard?
if you have mysql/mariadb, can you create the db and try with that configuration?
no, I'm using USB flash drive for the OS/Portainer and all the container data is written to an external SSD connected via USB. I'm using SQLite.
are you sure data is being written to the external drive? can you post the docker-compose?
Also, if you have the log of the container, just to check what's going on...
are you sure data is being written to the external drive? can you post the docker-compose?
Also, if you have the log of the container, just to check what's going on...
yes, I can see database.sqlite written to the SSD. the logs shows only "No log line matching the '' filter" until the container loads up.
version: '3.3' services: speedtest-tracker: container_name: speedtest-tracker ports:
Can you post the log from Portainer, with timesamp display set to on, this is mine, it takes 6 seconds:
_speedtest-tracker_logs (1).txt look at line 44, that's seems to be the problem. I can see heavy CPU usage "php-fpm: pool-www" until the container loads up successfully.
@ShlomiD83 I just released v0.2.0 which has arm v7 support (better rpi performance) let me know if this latest build changes anything for you.
@alexjustesen when I see the "Starting the queue worker..." can I assume the startup phase is completed and services are up? Or is there stuff still going on in the background? It would be good to be sure that last line of the log means startup is completed.
Also: the log doesn't provide timestamps...Portainer does luckily, otherwise we couldn't measure anything...
_speedtest-tracker_logs (1).txt look at line 44, that's seems to be the problem. I can see heavy CPU usage "php-fpm: pool-www" until the container loads up successfully.
This is your problem, but there are not enough details to debug it:
2022-11-04T11:37:13.834589600Z ❌ There seems to be a failure in checking the web server + PHP-FPM. Here's the response:
I also see this:
2022-11-04T11:37:11.923512689Z 🏃♂️ An SSL key was not detected, so I'll generate a self-signed SSL certificate pair for you...
You might want to map the certs folder for SSL, otherwise it will autogenerate it at every startup of the container, but on the RPi I would avoid it.
volumes:
- $PWD/config:/config
- $PWD/certs:/etc/ssl/web
_speedtest-tracker_logs (1).txt look at line 44, that's seems to be the problem. I can see heavy CPU usage "php-fpm: pool-www" until the container loads up successfully.
This is your problem, but there are not enough details to debug it:
2022-11-04T11:37:13.834589600Z ❌ There seems to be a failure in checking the web server + PHP-FPM. Here's the response:
I also see this:
2022-11-04T11:37:11.923512689Z 🏃♂️ An SSL key was not detected, so I'll generate a self-signed SSL certificate pair for you...
You might want to map the certs folder for SSL, otherwise it will autogenerate it at every startup of the container, but on the RPi I would avoid it.
volumes: - $PWD/config:/config - $PWD/certs:/etc/ssl/web
which certs to map? I didn't create any SSL certs.
@ShlomiD83 I just released v0.2.0 which has arm v7 support (better rpi performance) let me know if this latest build changes anything for you.
same behavior with v0.2.0 unfortunately.
which certs to map? I didn't create any SSL certs.
The container creates it for SSL connection.
2022-11-04T11:37:11.920350318Z 🏃♂️ Checking for Laravel automations...
2022-11-04T11:37:11.920468444Z 🔐 Linking the storage...
2022-11-04T11:37:11.922628080Z 🔐 SSL_MODE has set to FULL, setting the web server to work in HTTPS only...
2022-11-04T11:37:11.923512689Z 🏃♂️ An SSL key was not detected, so I'll generate a self-signed SSL certificate pair for you...
which certs to map? I didn't create any SSL certs.
The container creates it for SSL connection.
2022-11-04T11:37:11.920350318Z 🏃♂️ Checking for Laravel automations... 2022-11-04T11:37:11.920468444Z 🔐 Linking the storage... 2022-11-04T11:37:11.922628080Z 🔐 SSL_MODE has set to FULL, setting the web server to work in HTTPS only... 2022-11-04T11:37:11.923512689Z 🏃♂️ An SSL key was not detected, so I'll generate a self-signed SSL certificate pair for you...
so that's the high CPU reason? or a problem with the web server?
You might want to map the certs folder for SSL, otherwise it will autogenerate it at every startup of the container, but on the RPi I would avoid it.
No, I explained why in previous post. :)
It's a tiny optimization, it's not the problem you're having.
The problem you're having is the error in the log regarding php-fpm described in previous post.
You might want to map the certs folder for SSL, otherwise it will autogenerate it at every startup of the container, but on the RPi I would avoid it.
No, I explained why in previous post. :)
It's a tiny optimization, it's not the problem you're having.
The problem you're having is the error in the log regarding php-fpm described in previous post.
OK, how can we debug it further?
@alexdelprete @alexjustesen with v0.2.0 I don't see the PHP error in the logs but the container still takes time to load up. _speedtest-tracker_logs.txt
we need a debug level in the log...:)
let's wait for @alexjustesen to guide us on how to better debug this.
If you google...you'll find complaints about newer php-fpm versions causing performance issues on RPi.
But we're lucky because in your case there's an ERROR in the log...but the detail has been truncated.
@alexdelprete @alexjustesen with v0.2.0 I don't see the PHP error in the logs but the container still takes time to load up. _speedtest-tracker_logs.txt
I was googling, and read that there might be some caching going on to the boot drive (php-fpm), it means your usb drive.
Why didn't you use the wdred for boot + data? RPi supports booting from USB.
@alexdelprete @alexjustesen with v0.2.0 I don't see the PHP error in the logs but the container still takes time to load up. _speedtest-tracker_logs.txt
I was googling, and read that there might be some caching going on to the boot drive, it means your usb drive.
Why didn't you use the wdred for boot + data? RPi supports booting from USB.
the wdred was bought after the system was running for a few weeks, didn't want to reinstall everything.
the wdred was bought after the system was running for a few weeks, didn't want to reinstall everything.
You can clone the USB to wdred. I've used this in the past, it works fine: https://github.com/billw2/rpi-clone
The problem is for example that many apps use the system drive for various things, caching, /tmp, etc. so you can always face some issues.
the wdred was bought after the system was running for a few weeks, didn't want to reinstall everything.
You can clone the USB to wdred. I've used this in the past, it works fine: https://github.com/billw2/rpi-clone
The problem is for example that many apps use the system drive for various things, caching, /tmp, etc. so you can always face some issues.
OMV web UI didn't work after cloning, I've tried with other drives before.
the wdred was bought after the system was running for a few weeks, didn't want to reinstall everything.
You can clone the USB to wdred. I've used this in the past, it works fine: https://github.com/billw2/rpi-clone
The problem is for example that many apps use the system drive for various things, caching, /tmp, etc. so you can always face some issues.
that's the first time this kind of thing happens, I've spun up hundreds of docker containers on this RPi with no issue, so I doubt that the USB drive is the culprit here.
I've used it 2 times on two different RPi, an old RPi3 and a newer RPi4B, it always worked perfectly.
Anyway, you should really think about getting rid of the USB drive for system. Choose your preferred method to migrate.
hat's the first time this kind of thing happens, I've spun up hundreds of docker containers on this RPi with no issue, so I doubt that the USB drive is the culprit here.
on what basis you say that? if the container uses cache on the system drive, that would be your usb, and this is just one example.
which containers in your setup are using php-fpm? google php-fpm and rpi, you'll find a lot of issues.
good luck, I'll leave the rest to Alex. :)
php-fpm and rpi
according to "/etc/php/8.1/fpm/php.ini" there is no caching happening. session.cache_limiter = nocache
maybe that's not the issue?
edit: restarting the container after it loaded up successfully for the first time takes seconds. it appears only recreating the container causes it to load up very slowly.
maybe that's not the issue?
The issue is your hardware setup, not the container, you're the only person having to wait 8mins to startup a container. Setup your RPi properly. Running docker on a usb key in 2022 is not recommended by anybody, particularly when you have an external fast device attached used only for data and not for booting OS. Do your migration and your problem will be solved, like it was for this guy: https://www.reddit.com/r/NextCloud/comments/hrdpib/nextcloud_on_raspberry_pi_4_with_mariadb/
But as I said, I'm out of this conversation, you don't want to listen, you just want to pretend the container has a bug, which has not.
Goodbye, and good luck.
@alexjustesen thanks for trying to assist, I'll just keep using "henrywhitaker3/speedtest-tracker" for now.
maybe that's not the issue?
The issue is your hardware setup, not the container, you're the only person having to wait 8mins to startup a container. Setup your RPi properly. Running docker on a usb key in 2022 is not recommended by anybody, particularly when you have an external fast device attached used only for data and not for booting OS. Do your migration and your problem will be solved, like it was for this guy: https://www.reddit.com/r/NextCloud/comments/hrdpib/nextcloud_on_raspberry_pi_4_with_mariadb/
But as I said, I'm out of this conversation, you don't want to listen, you just want to pretend the container has a bug, which has not.
Goodbye, and good luck.
I took your advise and moved my OS to an SSD drive, now the container loads up in just under a minute. You've mentioned yours loads up in 7-8 seconds but I guess that's hardware dependent. (I'm using a RPi 4)
I took your advise and moved my OS to an SSD drive, now the container loads up in just under a minute.
Incredible how slow a USB drive is vs an SSD, isn't it? And now you also learned why booting the OS on the USB vs SSD is totally different, like I told you when you didn't want to listen. ;)
You've mentioned yours loads up in 7-8 seconds but I guess that's hardware dependent. (I'm using a RPi 4)
I use a Proxmox LXC container with docker on a Lenovo ThinkCentre M910x (Quad Core Intel Core i7-6700T), 32GB or RAM and a 1TB SSD. Can't really compare that to an RPi. And it's a desktop PC bought for $180. It runs a lot of stuff. Speedtest-Tracker starts in a few seconds, like other apps.
Hi, I've deployed the container on RPi 4 using docker compose with sqlite database. The log shows only "No log line matching the '' filter". The only thing I've changed is the port on the host side and the volume mapping.
Please advise.