The Internet suggested editing the Dockerfile to replace the offending COPY --CHOWN command with a COPY command followed by a RUN command that would do the chowning.
It seems to have worked and I now get to deal with having run out of space on the main drive. Progress!
drat, no dice
let's try docker-compose build --no-cache and see what happens
Step 29/38 : COPY --chown=mastodon:mastodon . /opt/mastodon
ERROR: Service 'streaming' failed to build: Unknown flag: chown
Building the new Docker image. Nap time!
Or meditation time, I've been slack on that lately.
Hooray, the copy of Git on the server doesn't wanna talk to Github "Permission denied (publickey)". There are a lot of hits for that so hopefully it should be easy to fix.
I ended up taking a shower and the backup was done when I got out, about 45 minutes after I started it. Also the Rez soundtrack just came to the end of the actual gameplay and is getting into the end credits music. Guess I'll do the next few steps while still around the house.
Or I could get dressed and go down to Envie and keep Nick company while he works. Get some exercise bicycling! Have coffee and power available for this task! Have someone to bite if it gets difficult!
Okay. Update day is here. I got the Rez soundtrack playing on the stereo and I am ready to get this done.
Keep an eye on @egypturnash for detailed updates as this happens.
Okay everyone looks like the image drive is totally full, this means image uploads won't work. Remote images will probably be weird too.
I'm gonna let the server keep running while I go get some food in me so I have some hope of having the energy to deal with this, I haven't eaten yet. Looks like it's properly saving toots at least. Just no new image uploads.
Someday I will get the automatic remote image cleanup task actually working reliably. Someday. Its unreliability has basically been the cause for every single outage this site's had.
We're back. Boring tech stuff details (letsencrypt/certbot update) behind the CW.
So this is what I had to do to deal with the fact that my default installation of Let's Encrypt will stop working in a month if I don't change the way it gets the certificate updated:
1. stop the system and back it up
2. sudo apt upgrade
3. apt install certbot
4. edit /etc/letsencrypt/renewal/dragon.style.conf and remove the reference to 'tls-sni-01' in 'standalone_supported_challenges'
5. change the /etc/cron.daily/letsencrypt-renew task to call certbot instead of letsencrypt
6. bring everything back up
and now hopefully this site should continue to connect via http without any further intervention on my part.
Hey y'all, I'm taking dragon.style down for a bit for some boring tech stuff. Keep an eye on @egypturnash for news. <3
*figures out how to restart it with a progress bar*
(rsync -a --info=progress2 --no-i-r SOURCE DEST)
this is gonna take ... a while.
Current dragon.style status: I got a new virtual drive attached to the server, and am copying over attachments. There's ~56 megs worth so I'm just gonna kick back and read; if I was at home I'd take another Spyro Break.
Once I get this done I get to convince nginx to serve files from the new drive. If I'm lucky a quick link will do the trick.
dragon.style status update: still down.
Trying to find information on how to move an instance's attachments from the local disc to somewhere else - ideally to one of Digital Ocean's "block storage" drives, but I'll take an S3/whatever guide if I can find it, as that's still better than flailing around blindly.
I posted about this on the Discourse: https://discourse.joinmastodon.org/t/migrating-static-data-to-digital-oceans-block-storage/1395, maybe I'll get something there.
Any help, #mastoadmins?
Awrite, looks like I am not going to be able to get enough space back by cleaning out remote media. I'm gonna spend the weekend setting up one of Digital Ocean's "block storage volumes" and moving attachments to that.
Hopefully things should be running again by Monday.
Enjoy your social media vacation. :)
Lackwit gadabout. Unnaturally colored hair. Draws.
Moved to https://dragon.style/web/accounts/1.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!