Having some trouble getting the Ghost docker container set up. I set up a MySQL8 docker to act as its database and set the username, password, and database name in the Ghost docker definition. The only thing I had to change is the port of the MySQL container since it uses the same port as my MariaDB container. I changed it, but the Ghost container doesn't have a place to specify a port for the database IP, and adding one seems to cause a connection error. When I use the raw IP and the correct login info, I get this error when starting the Ghost container:

 

14 hours ago, QuestForTori said:

Having some trouble getting the Ghost docker container set up. I set up a MySQL8 docker to act as its database and set the username, password, and database name in the Ghost docker definition. The only thing I had to change is the port of the MySQL container since it uses the same port as my MariaDB container. I changed it, but the Ghost container doesn't have a place to specify a port for the database IP, and adding one seems to cause a connection error. When I use the raw IP and the correct login info, I get this error when starting the Ghost container:

 

 

Create another variable in the container config in unRAID called

database__connection__port

Set that to the port used by your MySQL container

10 hours ago, cheesemarathon said:

 

Create another variable in the container config in unRAID called

database__connection__port

Set that to the port used by your MySQL container

Thanks! I put that variable in, but now I get a different error: 

(I'm sure that the database container is running and accepting connections, on the same virtual network as MySQL

Edited September 26, 20241 yr by QuestForTori

So what is the latest situation with Minio? is it working, or how to make it work?

On 9/13/2024 at 10:10 AM, sansi98 said:

You can use mergefs to merge multiple hard disks, and then minio uses the merged directory

Then map /mnt/addons/minio to the minio container

Note that it must be mounted in the /mnt/addons/ directory

mkdir -p /mnt/addons/minio
mergerfs  /mnt/disk1/minio:/mnt/disk2/minio /mnt/addons/minio

Does this work?

On 10/20/2024 at 5:32 PM, hodge.shen said:

Does this work?

yes，This is the docker configuration

 

This is the UNRAID file 

 

This is reading MINIO using the s 3 tool

 

 

 

But I work just as well with /mnt/user/minio

 

On 9/29/2024 at 1:05 PM, noonamer said:

So what is the latest situation with Minio? is it working, or how to make it work?

Yes it works, but its not as easy as it once was.

 

You can use mergefs to merge multiple hard disks, and then minio uses the merged directory

Then map /mnt/addons/minio to the minio container

Note that it must be mounted in the /mnt/addons/ directory

mkdir -p /mnt/addons/minio mergerfs /mnt/disk1/minio:/mnt/disk2/minio /mnt/addons/minio

On 9/26/2024 at 3:02 PM, QuestForTori said:

Thanks! I put that variable in, but now I get a different error: 

(I'm sure that the database container is running and accepting connections, on the same virtual network as MySQL

Have you actually connected to your database from another machine? Using something like MariaDB or DBeaver

Question about Metabase Docker

There is now a function that allows users to upload CSV and TSV files. Everything is set up in the frontend, but you get a permission denied when uploading and the file is not uploaded. Is this related to permissions or does it need an extra directory for the upload in the Docker settings?

 

Further background information Metabase is connected to a postgresql 14 database. The user has administration rights and therefore also write rights. The connection otherwise works perfectly. 

https://www.metabase.com/docs/latest/databases/uploads
https://www.metabase.com/docs/latest/databases/connections/postgresql

Edited November 1, 20241 yr by fritz_hh

I have now been able to solve it, but it is a bit bizarre. 
If you simply change the key1 to /tmp/, the database is recreated on a restart. If you then establish the connection in Metabase to the posgres database, everything works perfectly. 
I'm a bit surprised that you can't configure Metabase directly with postgresql in the Docker setup.

MB_DB_TYPE: postgres

MB_DB_DBNAME: metabaseappdb

MB_DB_PORT: 5432

MB_DB_USER: metabase

MB_DB_PASS: mysecretpassword

MB_DB_HOST: postgres

https://www.metabase.com/docs/latest/installation-and-operation/running-metabase-on-docker

Does Minio currently support the shfs filesystem?

I did not use mergefs，but it seems that minio works as well

It appears that something may have gone sideways with the latest Ghost update.  Getting this when updating, been working without issue for years:
 

Pulling image: ghost:latest
IMAGE ID [1073305513]: Pulling from library/ghost.

TOTAL DATA PULLED: 0 B

Error: manifest for ghost:latest not found: manifest unknown: manifest unknown

 

Anyone run into an issue with the minio container and it not starting after install?

 

Specifically the log shows

Fatal glibc error: CPU does not support x86-64-v2

 after I try to start it up.

 

I am assuming this is because of the hp microserver this is running on.  I would really really like to continue to use this as the only thing this box is doing is backups offsite.

 

The Microserver is a Gen7 I think (with the AMD Turion™ II Neo N40L Dual-Core).

 

Thoughts, comments and suggestions welcome on how I can get this back up and running.

 

On 12/2/2024 at 9:56 PM, Pela said:

Does Minio currently support the shfs filesystem?

I did not use mergefs，but it seems that minio works as well

I too just setup minio with a default mount of a share under users. I don't currently have but will shortly have a cache but it seems to be working? Curious if this can be considered supported or if I should look elsewhere for S3

With MinIO, files added to a bucket (backups from a separate Portainer box in this case) seem to end up with having the owner as `root` in terms of files, but my Nextcloud Docker container isn't able to scan them successfully due to the owner being `root`, which causes hundreds of errors in my Nextcloud logs.

 

Whilst I can set up a cron task to run a command to change the owner of everything in the dir every x amount of time, I'd rather sort out my perms properly for the MinIO container.

 

Does anyone have any pointers on this? This is probably midnight-brain in full-effect and very tired as it's been a long week. Hope you're all well!

Edited January 10, 20251 yr by Hammy Havoc

On 12/2/2024 at 8:56 AM, Pela said:

Does Minio currently support the shfs filesystem?

I did not use mergefs，but it seems that minio works as well

Sounds good! Perhaps there have been some changes to minio. But if you have it working thats great!

On 12/25/2024 at 4:13 AM, Delta said:

I too just setup minio with a default mount of a share under users. I don't currently have but will shortly have a cache but it seems to be working? Curious if this can be considered supported or if I should look elsewhere for S3

If you have it working, I'd consider it supported at this time!

13 hours ago, Hammy Havoc said:

With MinIO, files added to a bucket (backups from a separate Portainer box in this case) seem to end up with having the owner as `root` in terms of files, but my Nextcloud Docker container isn't able to scan them successfully due to the owner being `root`, which causes hundreds of errors in my Nextcloud logs.

 

Whilst I can set up a cron task to run a command to change the owner of everything in the dir every x amount of time, I'd rather sort out my perms properly for the MinIO container.

 

Does anyone have any pointers on this? This is probably midnight-brain in full-effect and very tired as it's been a long week. Hope you're all well!

try this in extra parameters 

--user UID:$GUID

replace UID and GUID with whatever you need for Nextcloud

Is anyone else having issues with their ghost container loading at all? I initially thought it was a SWAG issue, but I can't even get the 192 container address to load, it gives me a

 

An error occurred during a connection to 192.168.1.169:2368. SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

 

error. If I curl it (on http), I instead get a Moved Permanently status code with a redirect to https.

 

 

No clue where to go from here, tried a bunch of different settings, different networks, etc. Nothing in the ghost documentation looks like it disables ssl anymore, so I'm not sure how to get past this.

 

 

 

3 hours ago, snowe said:

Is anyone else having issues with their ghost container loading at all? I initially thought it was a SWAG issue, but I can't even get the 192 container address to load, it gives me a

 

An error occurred during a connection to 192.168.1.169:2368. SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

 

error. If I curl it (on http), I instead get a Moved Permanently status code with a redirect to https.

 

 

No clue where to go from here, tried a bunch of different settings, different networks, etc. Nothing in the ghost documentation looks like it disables ssl anymore, so I'm not sure how to get past this.

 

 

 

Ghost updated their docker image 2 days ago so i'm guessing this issue was created then. Quick fix would be to change the image to ghost:5.105

 

I'd then post your issue to the ghost forum as there are much more knowledgeable people there for ghost specific issues: https://forum.ghost.org/c/help/self-hosting/18 

13 hours ago, cheesemarathon said:

Ghost updated their docker image 2 days ago so i'm guessing this issue was created then. Quick fix would be to change the image to ghost:5.105

 

I'd then post your issue to the ghost forum as there are much more knowledgeable people there for ghost specific issues: https://forum.ghost.org/c/help/self-hosting/18 

It actually has been broken for a few months. I'll try posting in that forum though, thanks.

is it possible to use an zvol with Minio and if yes, how?

On 1/21/2025 at 12:53 AM, isvein said:

is it possible to use an zvol with Minio and if yes, how?

I know very little about ZFS but a quick google suggested this may work to create a zvol:

 

 

If you can get it mounted then you should be able to pass that through to minio by setting the mount point of the disk as the /data directory in the minio container config in unRAID

12 hours ago, cheesemarathon said:

I know very little about ZFS but a quick google suggested this may work to create a zvol:

 

 

If you can get it mounted then you should be able to pass that through to minio by setting the mount point of the disk as the /data directory in the minio container config in unRAID

Nice, you found my post on how I did it with iscsi XD

I tried to mount it with zfs mount but that did not work, because I was on that thought too

15 hours ago, isvein said:

Nice, you found my post on how I did it with iscsi XD

I tried to mount it with zfs mount but that did not work, because I was on that thought too

Ok in that case i'm not sure I can help you. You're in uncharted waters with regards to ZFS on unRAID as I'm sure your aware. I also couldn't find a huge amount of info on zvol's & minio so looks like you might have to do some more digging there too. TrueNAS forums might be a good place for info. Unfortunately for you this is way beyond my area of expertise. Good Luck and please report back if you do make any success!