cmer

I am struggling to connect two of my containers together. Basically, I have NextCloud running as "br0" and MySQL running as "bridge". I'd like to connect to MySQL from the NextCloud container, but it is not reachable when running as "br0". What steps should I take to be able to connect to MySQL TCP port 3306 from my NextCloud container? Thanks in advance

I am trying to setup a container with Network Type: br0. Oddly, I cannot reach my Unraid IP from inside the container. My pings just never make it to the host. I can reach it just fine when the container is in Bridge mode. Is there anything else I should be doing? Both IPs are on the same subnet (10.0.0.0/24). Thanks in advance.

Ah! That was easy! I had just removed the second drive from the cache pool, but did not set the cache slots back to 1. Thanks so much!

Hey guys, I found some info on the subject on the forum but not quite what I was looking for. I had a single cache drive formatted as XFS. I tried adding a second cache drive in slot 2, but now I get "Unmountable: No pool uuid", even after removing the second cache drive. I read that the default file system for cache drives is BTFRS. Could it be why I can't mount it anymore? Not sure what to do at this point. I don't want to lose the data I have on the cache drive (because I have more than cache data). Thanks!

I don't think Seafile upgrades the database automatically unfortunately... that's quite annoying. Maybe something I'll need to automate in a future version of this image. You need to run `upgrade/upgrade_6.1_6.2.sh` I believe. Docker-shell into the container while it's starting and apply it manually. I highly recommend this:

Can you post the logs?

6.4 indeed fixes the problem. Thanks!

Any update on this?

Great to know. I think I’ll upgrade.

Speaking of 6.4, how many more dozens of RC should we be expecting. Back in my day, RC meant release candidate, meaning unless there was a major blocker, it was going to be the production build

I am trying to run `kindlegen` in the Calibre-Web container. Unfortunately, it is a closed source, 32-bit i386 executable and it gives me the following error: `bash: vendor/kindlegen: cannot execute binary file: Exec format error` Is there a way to make this work? I can't recompile it since the source is closed. Thanks

Thanks guys, really appreciate the help!

I have an array of 16x3TB drives, including 2 parity. I currently have 2 drives giving me a SMART error. 1 parity and 1 data. The exact error is: "End-to-End Error, Failing now" with a count of 1 in Attributes. First of all, is it fair to assume that I should decommission those drives now? Second, what's the best way to do that? Many of my data drives are still empty, so I'd like to move the data from the failing data drive to an empty drive, and hopefully move the parity drive to another disk without rebuilding parity. Here are my assumptions. Maybe I'm wrong. - I can just `mv` files from /mnt/disk5 (failing) to /mnt/disk10 (new, empty) then remove disk5 from my array. - There is no way to move my parity drive without rebuilding parity. I'd have to decommission my failing parity drive, then assign parity to a new drive, then rebuild. I'm hoping for a way to avoid rebuild! What'd be the best way to proceed? Thanks!

Nevermind, Squid already did it I merged the PR.

Hmmm. Odd. If anyone wants to send a pull request to fix this, I'd be grateful.

Just ‘su’ to the correct user first.

The README has all the possible configuration options: https://github.com/cmer/docker-seafile

Folks, I just wanted to let you know that I have updated the image with the ability to set a specific version. This is useful if you want to run an older version, for example. All you need to do is set the VERSION environment variable. Please let me know if you run into any issues.

I have no idea. You should contact the people making Seafile to find out. They might be able to help.

Try going "pro" with the non-pro docker. I think you need to initialize the database with the community edition (non-pro) and then upgrade, but I might be wrong. Regardless, you can go back to non-pro without an issue after.

Have you tried starting the non-pro version first? Does that work?

Thanks. You do need a license but it's free. Get it from their website. I'd find it for you but I'm on the road right now...

You can't unless you also install the client on Unraid, which would definitely be an unconventional way of doing it. If you want to share /media, try using SMB.

This is the support thread for Minio, a distributed object storage server built for cloud applications and devops. It is available in Community Applications or at https://www.github.com/cmer/docker-templates.

Can you confirm it solved the issue you were having? thanks