Selfhosted

49406 readers

972 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

100

PSA: If the first Smart Search in Immich takes a while (lemmy.ca)

submitted 4 days ago* (last edited 4 days ago) by avidamoeba@lemmy.ca to c/selfhosted@lemmy.world

41 comments fedilink hide all child comments

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

[–] SheeEttin@lemmy.zip 0 points 4 days ago (7 children)

That seems like a bad idea

[–] ohshit604@sh.itjust.works 4 points 4 days ago* (last edited 4 days ago) (3 children)

As other stated it’s not a bad way of managing volumes. In my scenario I store all volumes in a /config folder.

For example on my SearXNG instance I have a volume like such:

services:
  searxng:
    …
    volumes:
      - ./config/searx:/etc/searxng:rw

This makes the files for SearXNG two folders away. I also store these in the /home/YourUser directory so docker avoids using sudoers access whenever possible.

[–] SheeEttin@lemmy.zip 1 points 4 days ago (2 children)

So why would you not write out the full path? I frequently rerun compose commands from various places, if I'm troubleshooting an issue.

[–] ohshit604@sh.itjust.works 3 points 4 days ago* (last edited 4 days ago) (1 children)

So why would you not write out the full path?

The other day my raspberry pi decided it didn’t want to boot up, I guess it didn’t like being hosted on an SD card anymore, so I backed up my compose folder and reinstalled Rasp Pi OS under a different username than my last install.

If I specified the full path on every container it would be annoying to have to redo them if I decided I want to move to another directory/drive or change my username.

[–] SheeEttin@lemmy.zip 1 points 4 days ago

I'd just do it with a simple search and replace. Have done. I feel like relative paths leave too much room for human error.

load more comments (3 replies)