Help installing container on TrueNAS Scale (containerd) about marqo HOT 6 CLOSED

Thanks @benedlore - I haven't tried running Marqo in this environment. I have a few questions:

1. can you access the Marqo logs?
2. is the machine arm64 or amd64 based?
3. Marqo requires the --privileged flag to run certain features. Is that possible in this environment? We may be able to run Marqo without this flag, but it may require configuration changes

from marqo.

Hi @pandu-k , thank you for responding.

They did have some options that I think should enable some of the args in the docker command:

I cannot see the marqo logs the same way as I can when running in Docker, but it does show some Kubernetes logs, although not sure they are very helpful. Mostly just saying the container is started and running type of thing:

 2023-11-15 16:43:34
Started container ix-chart
2023-11-15 16:43:33
Created container ix-chart
2023-11-15 16:43:31
Scaled up replica set marqo-ix-chart-6cfb8df7bd to 1 from 0
2023-11-15 16:43:31
Created pod: marqo-ix-chart-6cfb8df7bd-sslwp
2023-11-15 16:43:31
Successfully assigned ix-marqo/marqo-ix-chart-6cfb8df7bd-sslwp to ix-truenas
2023-11-15 16:43:31
Add eth0 [172.16.0.54/16] from ix-net
2023-11-15 16:43:31
Container image "marqoai/marqo:latest" already present on machine

Once it is reported as started and running, I have tried both on the TrueNAS machine and on a different device on same LAN to send some requests at it to see if it responds, but I always just get a "target actively refused connection"

from marqo.

Oh also, machine this is running on is amd64, an AMD Epyc Rome

from marqo.

I had my ports set up wrong, it works fine when properly setting container port to 8882: https://www.truenas.com/community/threads/help-with-a-docker-container-in-cobia-marqo.114234/#post-791323

from marqo.

@pandu-k Although it now works, I notice data is not persistent once it is turned off and back on. It has access to persistent storage space - do you know if there is a specific setting that might help with that?

from marqo.

I added the same env vars that the original container appeared to use, and then changed the mount path to "/var/lib/docker" and it appears to be saving the data persistently now!

from marqo.