After the Docker engine issue, we switched Mastodon to use persistent storages on disk for db volume.
In parallel, we upgraded to current master. There are some unidentified JS issues on Google Chrome, so we're rolling back to 1.4 (commit 4289ed1d13b9c3b91663581c44635105c4bc0412).
21:31: Mastodon images rebuild process launch
21:39: Precompiling JS / CSS / etc. assets (this operation generally takes a long time)
21:50: Assets compiled, trying to restart the server
21:55: All clear. Home feeds are lost, but will be regenerated on the fly (db has been restored, cache not). We switched to a permanent storage mode, so cache will be saved forever from now.