[NCP Docker] Hangs on 'Initializing NextCloudPi for the first time...'

Hey,

I just installed NextCloudPi/Plus as a docker container (Docker version 18.06.1-ce, build e68fc7a) with the following command docker run -d -p 4444:4443 -p 444:443 -p 81:80 -v ncdata:/data --name nextcloudpi ownyourbits/nextcloudpi-armhf 192.168.2.25. The only difference to the instructions are the different ports.
So, after downloading the newest image and starting the container i went trough the ‘activation process’ under https://192.168.2.25:444 where i got my passwords.
Under https://192.168.2.25:4444/ the login works and I can see the panel.
But everytime I now open https://192.168.2.25:4444/ it says

Initializing NextCloudPi for the first time

Please wait…

I deployed the container several times new and always deleted the volume/container before.

For me the logs seem to be

cat /var/log/ncp.log

[ nc-init ]
Setting up a clean Nextcloud instance... wait until message 'NC init done'
Setting up database...
Setting up Nextcloud...
Nextcloud was successfully installed
Set mode for background jobs to 'cron'
System config value mysql.utf8mb4 set to boolean true
System config value trusted_domains => 1 set to string 172.17.0.4
System config value trusted_domains => 5 set to string nextcloudpi.local
System config value trusted_domains => 7 set to string nextcloudpi
System config value trusted_domains => 8 set to string nextcloudpi.lan
[ nc-admin ]
System config value mail_smtpmode set to string sendmail
Successfully reset password for ncp

[ nc-passwd ]
password updated successfully
Enabling site ncp.
Enabling site nextcloud.
To activate the new configuration, you need to run:
  service apache2 reload
System config value mail_smtpauthtype set to string LOGIN
Site ncp-activation disabled.
To activate the new configuration, you need to run:
  service apache2 reload

System config value mail_from_address set to string admin
System config value mail_domain set to string ownyourbits.com
Error: Could not download app calendar

cat /var/log/mysql/error.log

2018-10-26  9:22:09 1995537760 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-10-26  9:22:09 1995537760 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-10-26  9:22:09 1995537760 [Note] InnoDB: The InnoDB memory heap is disabled
2018-10-26  9:22:09 1995537760 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-10-26  9:22:09 1995537760 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-10-26  9:22:09 1995537760 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-10-26  9:22:09 1995537760 [Note] InnoDB: Using Linux native AIO
2018-10-26  9:22:09 1995537760 [Note] InnoDB: Using generic crc32 instructions
2018-10-26  9:22:09 1995537760 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-10-26  9:22:10 1995537760 [Note] InnoDB: Completed initialization of buffer pool
2018-10-26  9:22:12 1995537760 [Note] InnoDB: Highest supported file format is Barracuda.
2018-10-26  9:22:12 1995537760 [Note] InnoDB: 128 rollback segment(s) are active.
2018-10-26  9:22:12 1995537760 [Note] InnoDB: Waiting for purge to start
2018-10-26  9:22:12 1995537760 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.1 started; log sequence number 1616918
2018-10-26  9:22:12 1371534128 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-10-26  9:22:12 1995537760 [Note] Plugin 'FEEDBACK' is disabled.
2018-10-26  9:22:12 1995537760 [Note] Recovering after a crash using tc.log
2018-10-26  9:22:12 1995537760 [Note] Starting crash recovery...
2018-10-26  9:22:12 1995537760 [Note] Crash recovery finished.
2018-10-26  9:22:12 1995537760 [Note] Server socket created on IP: '127.0.0.1'.
2018-10-26  9:22:12 1995537760 [Note] mysqld: ready for connections.
Version: '10.1.26-MariaDB-0+deb9u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian 9.1

cat /var/log/php7.2-fpm.log

[26-Oct-2018 09:22:00] NOTICE: fpm is running, pid 74
[26-Oct-2018 09:22:00] NOTICE: ready to handle connections
[26-Oct-2018 09:22:00] NOTICE: systemd monitor interval set to 10000ms

Do you have any ideas? Thanks for any answers :).

Have you fixed it somehow? I have the same issue like you…

Solution to same issue in this post.
If you are running docker on rpi, it can take very looooong time to initialize. Wait for init done in log.

I have waited 6 hours… “very loooong time” is so long?
this is my log: docker logs -f nextcloudpi

Initializing empty volume…
Making /usr/local/etc/ncp-config.d persistent …
Making /etc/services-enabled.d persistent …
Making /etc/letsencrypt persistent …
Making /etc/shadow persistent …
Making /etc/cron.d persistent …
Making /etc/cron.daily persistent …
Making /etc/cron.hourly persistent …
Making /etc/cron.weekly persistent …
Making /usr/local/bin persistent …
Making /etc/apache2 persistent …
Starting PHP-fpm
Starting Apache
Starting mariaDB
2019-10-27 14:57:36 0 [Note] mysqld (mysqld 10.3.15-MariaDB-1) starting as process 103 …
Starting Redis
Starting Cron
Starting Postfix
Uninitialized instance, running nc-init…
Running nc-init
Setting up a clean Nextcloud instance… wait until message ‘NC init done’
Setting up database…
Setting up Nextcloud…
Nextcloud was successfully installed
Set mode for background jobs to ‘cron’
System config value tempdirectory set to string /var/www/nextcloud/data/tmp
System config value mysql.utf8mb4 set to boolean true
System config value trusted_domains => 11 set to string ***.***.***.***
System config value trusted_domains => 1 set to string ***.***.***.***
System config value trusted_domains => 5 set to string nextcloudpi.local
System config value trusted_domains => 7 set to string nextcloudpi
System config value trusted_domains => 8 set to string nextcloudpi.lan
System config value mail_smtpmode set to string sendmail
System config value mail_smtpauthtype set to string LOGIN
System config value mail_from_address set to string admin
System config value mail_domain set to string ownyourbits.com
nextcloudpi enabled
Error: Could not download app calendar
Init done

if I go with browser:

Initializing NextCloudPi for the first time

Please wait…

Thanks

Same here. Could use help. I had it working fine, until i installed letsencrypt docker, then everything started to crash, now i cant seem to get it to install fresh again. I am new to this. maybe the reverse proxy has a setting idk.

any help wanted.