Thor

Seems like Sonarr v2 is EOL and v3 is stable now I guess this docker instance will automatically update without changing tags in the near future?

Got the same issue as you @maartenweyns.

I got the same issue as @Hernaldo. Is it salvageable?

Having an issue with my Gitlab-Ce instance. It is fully updated (and it ran perfectly before), however when I start Gitlab, I get the following: Running handlers:[0m There was an error running gitlab-ctl reconfigure: bash[migrate gitlab-rails database] (gitlab::database_migrations line 55) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1' Running handlers complete ---- Begin output of "bash" "/tmp/chef-script20200709-25-jjrrc7" ---- STDOUT: rake aborted! PG::ConnectionBad: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"? /opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/db.rake:48:in `block (3 levels) in <top (required)>' /opt/gitlab/embedded/bin/bundle:23:in `load' /opt/gitlab/embedded/bin/bundle:23:in `<main>' Tasks: TOP => gitlab:db:configure (See full trace by running task with --trace) STDERR: ---- End output of "bash" "/tmp/chef-script20200709-25-jjrrc7" ---- Ran "bash" "/tmp/chef-script20200709-25-jjrrc7" returned 1

Seems like there are multiple people having issues with this, which is great! Then perhaps, if the developers have some time left, that they can check out our issue

I think it will be pushed further up the devs todo list if more people experience and notify them about it

Hello, my first post ever here, so I just have to use the opportunity to say what an amazing product unRaid is However, I too have the samme issue as OP. Its seems that my poor little SSD has written around 50TB of data on it. (Bought June 2019, only used for unRaid). I was for a long time on version 6.7, but after upgrading directly to 6.8.3, I started getting a lot of notifications about excess heat on my SSD and saw that something wrote massively to the drive. I checked every docker app, turned them off - but still had the issue. (At the same time as upgrading the unRaid version, I also did extend my docker image to have more space, since I had to stop the array/boot the server anyways.) I almost never got notifications about excess heat on 6.7. (EDIT: as a result of the massive writing of course) This led me to googling and finding this post. I implemented the solution described here, and it worked! No more constant write and heat notifications on my SSD drive( BTRFS, encrypted). A bit scared to boot the server now, since I know rc.docker will reset. (Will it however boot my docker apps as normal, even without the symlink?)