12·
7 months agoIt’s a relatively low performance hit and it benefits me when having to replace a failing/old disk. I can just toss the drive without having to erase the data first, that is as long as the key is a secure length.
A Mouse
- 0 Posts
- 20 Comments
Joined 1 year ago
Cake day: June 1st, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
~53 W
-
Server:
- AMD Ryzen 5 5600G
- 4x16 GB DDR4 3200 Mhz
- 256 GB NVMe as boot-disk
- 2x256 GB Samsung SSDs for VMs
- 2x2 TB WD Red Plus HDDs
-
Mini PC: Beelink S12 N95
- 16 GB DDR4
- 256 GB NVMe
-
8 port unmanaged TP Link switch
I would like to expand my storage, however I don’t have any available SATA ports and I believe adding an HBA would increase the idle draw about 8 W. I might just upgrade the SSDs and split the storage between the HDDs and SSDs.
-
I recently switched from Proxmox to Debian Bookworm with Incus(LXD fork) as my primary setup, it’s been a pleasant experience. I also like the idea of using something like Cockpit to manage VMs though haven’t come to a need yet for a VM over a container. I’ll also point out that Incus can handle VMs as well.
Stéphane Graber, Project leader of Linux Containers is also on the fediverse and responds to questions often.
That’s a good recommendation, thanks!
There’s even an RSS feed for that page: https://openwrt.org/feed.php?mode=list&ns=advisory
You’re welcome! Also thanks for asking this question, I hadn’t seen ShotShare before, it looks useful.
No, since you are using the bind mount, you do not need to use the volume.
I just did another test.
You should be able to create the directories manually. I cheated by simply cloning the repo and copying them to the bind mount location like so. You can use the bind mount method like you wanted.
git clone https://github.com/mdshack/shotshare cp -r shotshare/storage/* /srv/dev-disk-by-uuid-7fe66601-5ca0-4c09-bc13-a015025fe53a/Files/Shotshare/shotshare_data/ chown 82:82 -R /srv/dev-disk-by-uuid-7fe66601-5ca0-4c09-bc13-a015025fe53a/Files/Shotshare/shotshare_data
It will be stored in
/var/lib/docker/volumes, you can find the exact location by inspecting the volume. Usedocker volume lsto list the volumes, and dodocker volume inspectreplacing with the one from the list. Look for “Mountpoint”, that is the exact location. You could try copying that to bind mount location, though I can’t be sure if it will continue to work.
This appears to be the exact same problem as https://github.com/mdshack/shotshare/issues/31
For testing I just spun up a VM with Docker, I tried the same compose file as you. I found I had to use the volume instead of a bind mount for
/app/storage.This compose file should work.
version: "3.3" services: shotshare: ports: - 2000:80 environment: - HOST=:80 - ALLOW_REGISTRATION=false volumes: - shotshare_data:/app/storage - /srv/dev-disk-by-uuid-7fe66601-5ca0-4c09-bc13-a015025fe53a/Files/Shotshare/database.sqlite:/app/database/database.sqlite - /srv/dev-disk-by-uuid-7fe66601-5ca0-4c09-bc13-a015025fe53a/Files/Shotshare/.env:/app/.env restart: unless-stopped container_name: shotshare image: mdshack/shotshare:latest volumes: shotshare_data: networks: {}
That error message says it the permissions of the
/home/user/Documents/Docker/LinguaCafe/logsdirectory. You can try changing it full r/w temporarily to test.
I like it, then it’s even harder to know that it was encrypted in the first place. Thanks for that suggestion.
You will need to create a network bridge: https://www.truenas.com/docs/scale/23.10/scaletutorials/virtualization/accessingnasfromvm/ Also more information in the Setting up NFS for Portainer section of this guide: https://forum.level1techs.com/t/truenas-scale-ultimate-home-setup-incl-tailscale/186444
While this wouldn’t work for you now, something to think about is encrypting new drives going forward so that you don’t have to worry about erasing/zeroing them, just toss the encryption key and your good to go.
Using your own router is the best way, I just finished setting up DoH, I am using a router with OpenWRT, so installed https-dns-proxy with luci-app-https-dns-proxy. It has options to hijack DNS so that all local devices will be routed to the router DNS even if they try to use a DNS server directly.
More information can be found here.
There was a point I had a minimum of one service from each category of the awesome-selfhosted repo. I’ve since scaled down to a more minimal approach, but still enjoy looking for new services to try out.
Monitoring is one that’s interesting, graphs can be fun to look at though, so Grafana for that, and it’s fun for family to see, even if they don’t exactly know what it means, lines and charts are pretty.
I have since setup most of my monitoring to only alert if there is something that is unusual or outside of some threshold. Previously I had it alert me when a process or script had finished, however it was too noisy, and instead now it checks to make sure the script succeeded and if it didn’t to alert me.
- Categories
- Main
- Docker
- UptimeKuma
- Video
- Plex
- Overseer
- Tautulli
- Wizarr
- Audio
- moOde Audio
- Audiobookshelf
- Your Spotify
- Books
- Calibre-Web
- Calibre
- Downloads
- SabNZBD
- qBittorrent
- Cloud
- Immich
- Filerun
- Pairdrop
- Syncthing
- Paperless
- Home
- Home Assistant
- Mealie
- Node RED
- Productivity
- FreshRSS
- Linkding
- Obsidian
- Starr Apps
- Prowlarr
- Jackett
- Radarr
- Sonarr
- Sonarr Anime
- Readarr Audio
- Readarr Books
- Kapowarr
- Lidarr
- Website
- SerpBear
- Umami
- Utilities
- FileFlows
- Changedetection.io
- Stirling-PDF
- OpenSpeedTest
- Adminer
- Radicale
- Network
- PiHole
- PiHole - IoT
- Speedtest
- Main
- Categories
- Categories
- House
- Home Assistant: front-end
- Frigate: CCTVs and NVR
- Node-RED: node.js automations
- ESPhome: IoT devices
- Homelab
- Grafana: Monitoring data
- Pi-hole (primary): Local DNS & ad blocking
- Pi-hole (secondary): Local DNS & ad blocking
- Portainer: Docker container management
- Proxmox #1: PVE node: chewy
- Proxmox Backup #1: PBS node: chewy
- Proxmox #2: PVE node: hansolo
- Proxmox Backup #1: PBS node: hansolo
- Nginx Proxy Manager: Reverse proxy server
- Media
- nzbget: Usenet downloading
- Deluge: Torrent downloading
- Plex: Media server
- Overseerr: Media library management
- Tautulli: Plex reporting
- Prowlarr: Indexer managerment
- Data
- Paperless-ngx: Document management
- Photoprism: Photo library
- Calibre: eBook library
- Readarr: eBook management
- Sync thing: File sync
- Joplin Server: Notebook sync
- Homelab Devices
- Firewall: OPNsense on Proxmox
- Primary NAS: Netgear ReadyNAS NV+ V2
- Secondary NAS: Qnap TS-410
- Switch: Netgear GS324TP
- Wifi: Aruba IAP-225 Virtual controller
- Printer: Fuji Xerox CM115w
- Health
- rey: Raspberry Pi 4
- lando: Raspberry Pi 3
- quigon: Raspberry Pi 3
- bobafett: Raspberry Pi 2
- jangofett: Raspberry Pi 3
- Databases
- Prometheus: Pi-hole stats
- InfluxDB: Timeseries databases
- Radius DB (Adminer): PostgreSQL database
- Tools
- VS Code: Remote code editor
- searxng: Private web search
- Changedetection: Monitor website changes
- Octoprint: 3D printing
- Shellinabox: Ajax console client
- Media Libraries
- Sonarr: TV show library
- Sonarr (anime): Anime TV show library
- Radarr (4K): 4K movie library
- Radarr: Movie library
- Radarr (Anime): Anime movie library
- House
- Categories
I use names of mice from popular movies and TV shows. I use this list.
I know it’s not useful, but it’s fun to me. I would never use it in a professional environment.
As a small homelabber I agree with this. I started with a baremetal and using Docker, and switched to Proxmox, and now over to Incus, actually currently I am using Debian with cockpit + cockpit-machines. I do like Incus, I keep hopping back and forth between cockpit, I need to settle on one.