Persistent Extension Installation Issue After Container Restart

Phixel

Hello Flarum Community,

I’m running a Flarum forum in a Docker environment and have encountered an issue where extensions installed via Composer (e.g., afrux/asirem) disappear after the container is restarted. I suspect this might be due to the ephemeral nature of the container’s file system or a misconfiguration with persistent volumes.

Could someone please provide guidance on how to ensure that installed extensions remain persistent across container restarts? Any advice or best practices for handling this in a Docker setup would be greatly appreciated.

Thanks in advance for your help!

Best regards,
Phixel

luceos

Phixel it depends on how you use docker. Make sure that the composer files and vendor folder are persisted/used from the host machine.

Phixel

I am gonna lose my mind. I trying to setup a persistent folder with ChatGBT Pro for and the whole internet fo fours. That don't work. I am not familiar with this whole system. Is there a easy way to setup up a persinstent folder where I can install my extensions. That can be that hard...

luceos

Phixel can you share you docker and/or docker-compose files? That would be a great start.

Retcon01

I have a Flarum install on PikaPods, which I think uses docker, and this is from their documentation. I have to do this to persist extension installs.

To persist extensions during pod updates and edits, you also need to add the vendor/package-name in the file /data/extensions/list. This file can be accessed via SFTP. Be sure to have a new line at the end of the file. (We are working to get rid of this step.)