this post was submitted on 13 Mar 2026
1423 points (98.9% liked)

Selfhosted

59973 readers
425 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] nucleative@lemmy.world 18 points 3 months ago* (last edited 3 months ago) (2 children)

Never run:

docker compose pull
docker compose down
docker compose up -d

Right before the end of your day. Ask me how I know ๐Ÿ˜‚

[โ€“] shym3q@programming.dev 9 points 3 months ago (1 children)

compose up will automatically recreate with newer images if the new one were pulled. so there is no need for compose down btw

[โ€“] nucleative@lemmy.world 2 points 3 months ago

You're right. I got in the habit of doing that because I'm endlessly tweaking my .env files and I don't think those reload unless you shut down first

[โ€“] irmadlad@lemmy.world 2 points 3 months ago

Right before the end of your day

Oh, gosh, I did this last evening. I didn't check what time it was, and initiated an update on some 70 containers. I have a cron that shuts down the server in the evening, and sure enough, right in the middle of the updates, it powered off. I didn't even mess with it and went to bed. Re-initiated the update this morning, and everything is up and running. Whew!