Upgrade of container results in lost database config about docker-flarum

[hardware]

Flarum container volumes are not properly defined, you must use two differents volumes, one for extensions and another for assets. Like this :

volumes:
  - xxx:/flarum/app/assets
  - xxx:/flarum/app/extensions

It's not a good idea to store /flarum/app/ entire directory with a named docker volume.

Did you lose data in /flarum/app/assets directory ? Check if /flarum/app/asset/rev-manifest.json exist. If not, create it manually with touch because the boot script use this file to know if an installation has already been performed.

docker-flarum/rootfs/usr/local/bin/run.sh

Lines 57 to 58 in 990087f

	# if no installation was performed before
	if [ -e 'assets/rev-manifest.json' ]; then

docker exec -ti flarum touch /flarum/app/asset/rev-manifest.json && chown $UID:$GID /flarum/app/asset/rev-manifest.json

[Braintelligence]

Thank you for clarifying. I wanted to not create two separate volumes, since volume-subfolders are not supported yet ☹️, so I tried just mounting to the whole app folder. Seems like it was a bad idea.
Actually even restarting removed the config.php. Gonna try using two volumes now.

[hardware]

You can create two named volumes with rancher :

volumes:
  flarum-assets-vol:
    driver: local
  flarum-extensions-vol:
    driver: local

services:
  flarum:
    volumes:
      - flarum-assets-vol:/flarum/app/assets
      - flarum-extensions-vol:/flarum/app/extensions

[Braintelligence]

I know, I just didn't want to clutter my rancher instance with more volumes than needed, so I tried with one volume for the whole Flarum service 😸.

[hardware]

Actually even restarting removed the config.php. Gonna try using two volumes now.

config.php is automatically created by the boot script when the container starts and if an installation has already been performed (rev-manifest.json). You do not have to worry about it.

I know, I just didn't want to clutter my rancher instance with more volumes than needed, so I tried with one volume for the whole Flarum service smile_cat.

Okay 😸 Tell me if this has solved your problem.

[Braintelligence]

I deleted the contents of var/lib/mysql in the mariadb container and try to reinstall everything anew. But sadly I get this at the installation page, even though DEBUG = true:

I have no idea what the problem is now 😛

EDIT: Found the culprit. I set PHP_MEMORY_LIMIT to 256 instead of 256M.
Now I get this, though:

[Braintelligence]

Okay, deleting the var lib mysql again and restarting everything solved it. Now I'll set everything up again and try upgrading the flarum container again and see if it works 😸.

EDIT: Did you run into problems running flagrow bazaar with your default config? It seems to kill Flarum everytime I try to run it.

[hardware]

Did you run into problems running flagrow bazaar with your default config ? It seems to kill Flarum everytime I try to run it.

I don't know if this docker image supports it, probably not. You can open another issue for this or a pull request if you manage to make it work.

[Braintelligence]

Ok, so when I upgrade the container all the third party extensions are being removed =/

[hardware]

With two separated volumes ?

[Braintelligence]

Yes.

EDIT: Forum threads and everything is still there, so the config.php is being kept.

[hardware]

Check if your extension volume is persisted by rancher. If yes, your flarum/extensions/list file must contains all your installed extension with docker exec -ti flarum extension. If this file is empty or inexistent, maybe you have a storage issue with rancher.

Which command do you use to install an extension ?

Follow this instructions to install an extension :
https://github.com/mondediefr/docker-flarum#install-custom-extensions

Rancher storage documentation :
https://rancher.com/docs/rancher/latest/en/rancher-services/storage-service/