A true man of culture, I see 🫡

Huh!, just Disconnect the drive from power source and it will OFF.

Please refer to this comment: https://lemmy.ml/comment/24567541

If you need any further information, let me know.

Note that I’m running it on a rootless docker instance, and NOT on Podman. So, the following solution might or might not work for you.

services:
  degoog:
    image: ghcr.io/fccview/degoog:latest
    volumes:
      - ./.data:/app/data
    user: "0:0"
    ports:
      - "4444:4444"
    restart: unless-stopped

Explanation: rootless docker works a bit different from rootful docker. user 1000 (which is you on your server/machine) will be mapped to a different UID (e.g. 32555). This is to ensure that any process in docker container can’t have access to folders/files that you have access to, in case it manages to break free of docker containerization.

When you put user: “0:0” in a rootless docker container, it will assume your UID 1000 (which is you on your server/machine) inside docker container.

While it solves the file permission issue, but it is NOT a recommended way.

with user:1000:1000

with user:0:0

Ah! Forget about that part. The docker-compose file you provided on repo works for rootfull docker.

For rootless docker, it works, but library import is not possible for file permission issue.

I think I know how to solve it, I will give it a try over weekend, and will let you know.

First of all, thanks a ton.

I have been using SearxNG for more than year, running it as docker container on my Homelab. It’s connected to internet via Mullvad VPN.

Lately, I have see both Google and Bing search engines are either not working or returning complete garbage results.

My firewall setup doesn’t allow any incoming connection to homelab, except from LAN. So, bot accessing my SearxNG instance might not be the issue.

With degoog installed in the same fashion (docker + VPN), google engine seems to be unblocked for me (so far).

Not sure why degoog is not getting rate limited like SearxNG on the same system and same VPN. But, at least I’m happy :)

Tailscale, if you don’t want to make your services available to anyone else than you (and people you want to grant access to).

Thumb rule: whichever I feel comfortable with in a given situation, I use.

https://github.com/element-hq/synapse/blob/develop/contrib/docker/docker-compose.yml

At workplace, use whatever OS and tools allowed by company policy.

At home, use whatever OS and tools you like.

At least that is how I’m managing it.

Isn’t Podman rootless by default, unlike docker?

All the countries need to use ‘Open sourced’ product, IMO.

Thanks a lot :)

From developers point of view, maintaining one codebase that works across OSs is better than maintaining OS specific multiple codebases.

Nice. After Bilbogram was discontinued, I believe we all were waiting for an replacement.

• AdguardHome
• Nextcloud
• Redlib
• DrawIO
• Wireguard
• Matrix server
• SearxNG
• Jellyfin
• LibMedium
• Linkwarden
• IT-tools
• Vaultwarden
• Memos
• Miniflux
• Rimgo
• Invidious
• Quetre
• Anonymously Overflow

All except few are routed via VPN.

Hosted on: Raspberry Pi 4B + Alienware M14x R2

I had to sell my kidney to buy one RAM yesterday /s

Ubuntu 25.10 + Wayland + Gnome 49 + Nvidia driver v580.95 (RTX 3070 Ti) works flawlessly for both gaming and normal apps.

Anything other than rolling release, as stability matters more when you are dealing with server setup. So, Ubuntu LTS, Debian should be good fit.

My 12 years old Alienware M14x R2 [1] is doing great as a homelab. I have the following services running on rootless docker container:

1. Nextcloud AIO
2. Element
3. AdguardHome
4. Jellyfin
5. SearxNG
6. Vaultwarden
7. … and few other services as well

So far, I managed to utilized around ~6 GB out 16 GB RAM. Throughput wise, it is doing great (over LAN and over Tailscale).

If you have any old laptop unutilized, you may try to repurpose it as one of your homelabs.

[1]https://dl.dell.com/manuals/all-products/esuprt_laptop/esuprt_alienware_laptops/alienware-m14x-r2_reference guide_en-us.pdf