this post was submitted on 08 Jul 2025
105 points (97.3% liked)

Selfhosted

49326 readers
514 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 posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

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

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Your ML model cache volume is getting blown up during restart and the model is being re-downloaded during the first search post-restart. Either set it to a path somewhere on your storage, or ensure you're not blowing up the dynamic volume upon restart.

In my case I changed this:

  immich-machine-learning:
    ...
    volumes:
      - model-cache:/cache

To that:

  immich-machine-learning:
    ...
    volumes:
      - ./cache:/cache

I no longer have to wait uncomfortably long when I'm trying to show off Smart Search to a friend, or just need a meme pronto.

That'll be all.

you are viewing a single comment's thread
view the rest of the comments
[–] wabasso@lemmy.ca 3 points 2 days ago (11 children)

Ok I should know this by now, but what actually is the current “./“ directory when you use that? Is it the docker daemons start dir like /var/docker ?

[–] mhzawadi@lemmy.horwood.cloud 6 points 2 days ago (9 children)

./ will be the directory you run your compose from

[–] SheeEttin@lemmy.zip -1 points 2 days ago (7 children)
[–] MangoPenguin@piefed.social 8 points 2 days ago (1 children)

Its convenient because your data is stored in the same folder that your docker-compose.yaml file is in, making backups or migrations simpler.

[–] avidamoeba@lemmy.ca 2 points 2 days ago

Yup. Everything is in one place and there's no hardcoded paths outside of the work dir making it trivial to move across storage or even machines.

load more comments (5 replies)
load more comments (6 replies)
load more comments (7 replies)