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.
That’s interesting! I wonder if they are locking down factory installations.
About a month ago I was able to do it with a fresh install of Pro in a VM, I’ll do a quick test and see if it works on Home…and it works too. I had to disconnect the network and then run the OOBE\BYPASSNRO command, it rebooted and gave me the continue without network and limited setup options.
Unless I missed something, the article states as follows
Another method of bypassing the account lockdown still exists. You simply have to enter OOBE\BYPASSNRO in the command prompt during the Windows 11 setup process, which allows you to skip the connection to the Internet and thus also the link to a Microsoft account.
I agree. I am someone who values their privacy and often does not like opt-out style analytics however I also know opt-in skews analytics. The way the searches are only categorized, and they are using Oblivious HTTP keeping IP addresses private makes me A-OK with this.
It’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.
~53 W
Server:
Mini PC: Beelink S12 N95
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. Use docker volume ls to list the volumes, and do docker volume inspect <volume_name> replacing <volume_name> 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/logs directory. You can try changing it full r/w temporarily to test.
So, I just walk into the film studios lobbies(Everyone of them) and ask them for an Ethernet cord, I proceed to connect my NAS to it and download every movie released by that same film studio. I’ve never had an issue from them.
Because, everything on the internet is true, right? Maybe I posted a totally false statement because it sounds good on the area of the internet I posted, or maybe I didn’t make a totally inaccurate and false statement and want everyone to know how amazing it is. The world will never know!
You can still use old.reddit.com
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
I agree with this. I understand that the majority of users also don’t read release notes and some don’t even install add-ons, with this being enabled by default this would provide them with a more anonymous ad experience.