Minio Replication on Truenas Scale

tom6475

Cadet
Joined
Jul 1, 2022
Messages
2
Hello,
I've just upgraded to latest release of Truenas Scale (TrueNAS-SCALE-22.02.2), and I would like to use Minio Replication.between two truenas Scale. (active / active one)

By using the official application (minio) but also trying to use the truechart one, I can see that the feature seems to be present in the minio UI, but it seems it can not be used.

By having a look at the minio documentation, replication needs the mc binary (https://docs.min.io/docs/minio-bucket-replication-guide.html), and it seems this binary is not present in the docker image (either the official one or the truecharts one).

Do you know I could do to implement active / active replication on truenas scale ?

Thanks

Thomas
 

qmcb23YR

Dabbler
Joined
Mar 30, 2020
Messages
12
Correct, mc requires another docker container. Both container networks need to talk to each other, else this won't work.

Can be installed from https://hub.docker.com/r/minio/mc/ or as a static binary from https://dl.min.io/client/mc/release/linux-amd64/mc.


The below needs to be changed pending your set-up, but should give you a rough idea of how to get started should you prefer to use docker. Else you can jump straight to line 2.


Code:
docker run --net=host -it --entrypoint=/bin/sh minio/mc
mc config host add minio http://127.0.0.1:9000 access_key access_key_secret
 

stavros-k

Patron
Joined
Dec 26, 2020
Messages
231
Apps have internal communication with their internal DNS. In this case all you need is the "mc" container to be added by someone (or yourself) as an "App"

Then you run the command on line 2 and you are ready.
 

tom6475

Cadet
Joined
Jul 1, 2022
Messages
2
Hello,

Thanks for your answer. Using the CLI, and with your hints, I've been able to launch minio/mc docker, then minio replicitation is easy. But I would like minio/mc to be installed as an application. I've tried to do it using the webui wizard of truenas "Launch Docker Image", but the docker doesn't seems to get deploy properly (it stays in deploy state).

The error is

{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"container \"ix-chart\" in pod \"mc-ix-chart-7c886c7fbc-w8xqc\" is waiting to start: CreateContainerError","reason":"BadRequest","code":400}

Thanks

Thomas
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,700
The error is

{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"container \"ix-chart\" in pod \"mc-ix-chart-7c886c7fbc-w8xqc\" is waiting to start: CreateContainerError","reason":"BadRequest","code":400}
That would indicate some parameter you specified for the app is wrong or there is a problem with accessing the path supplied (permissions).
 
Top