If you’re using the Docker image, then it would probably be smarter to link the plugins directory to a volume outside the image - otherwise it would be destroyed when you upgrade.
So silly I did not check the logs before, I am getting:
May 31 20:32:41 WARN metabase.plugins :: Metabase cannot use the plugins directory /app/plugins
Please make sure the directory exists and that Metabase has permission to write to it. You can change the directory Metabase uses for modules by setting the environment variable MB_PLUGINS_DIR. Falling back to a temporary directory for now.
java.lang.AssertionError: Assert failed: Metabase does not have permissions to write to plugins directory /app/plugins
(Files/isWritable <>)
Completly overlooked the folder permissions. Thanks for pointing that out and giving me the references. The connection worked!
I am completly new to Docker & Metabase so I was just trying some basic stuff. Do you have any other references for me that I need to take in mind, I will be sure to read and try to execute the two you send me.
@GorkyV
Well, the thing that most people tend to misunderstand with containers is; networking.
You have to think of each container as it’s own server. The container can then be “linked” with storage/networks outside the container (like bridging to between containers).
If you’re new to Docker, then you should probably read their documentation: https://docs.docker.com/
The most important thing with Metabase is just make sure you’re not running the H2 database inside the container - preferably not using H2 at all.
Then you won’t lose data, when you upgrade.
A lot of other things (how to use Metabase etc) are covered in the documentation: https://metabase.com/docs/latest/