IIRC docker on Windows lives inside WSL, so everything is done on Linux anyway. What’s the issues you’re getting?

The typical way involves something outside your network acting as a proxy. Your home network VPNs to this proxy, then the proxy sends requests down to your homelab.

I used a VPS and a VPN, I would connect to the VPN endpoint on the VPS, and then route all traffic back down to home.

You can also run a reverse proxy on the VPS, so it does TLS for clients, and speaks to the servers direct over the VPN.

Another option is things like Cloudflare tunnels, which means cloudflare does the “VPS and VPN” part of the above, but the tradeoff is that your have to trust cloudflare, rather than yourself (may be a positive or not depending on your perspective).

Lastly you could use something like tinc (which needs something on the outside to act as a negotiator) to form a mesh between NAT’d devices.

It means that if someone breaks out of your container, they can only do things that user can do.

Can that user access your private documents (are these documents in a container that also runs under that user)?

Can that user sudo?

Can that user access SSH keys and jump to other computers?

Generally speaking, the answer to all of these should be “no”, meaning that each group of containers (or risk levels etc) get their own account.

There’s mt32-pi, a baremetal app that emulates the classic MT-32 MIDI synthesizer.

For better or worse, the Pi (2+) seems to be the only SBC with a video output that can do 240P or other funky CRT resolutions (the DPI interface on the GPIO).

Not quite, I have to go through out of box, and then join it to the domain, but then yes!

Applies security policy, install apps, disables bloat, login in with central username and pass, get mapped drives etc

I have a Windows AD domain and have my preferences and some apps as GPOs.

In the server world we use Ansible, or in some cases maybe PowerShell DSC.

Ansible is much more focused on Linux and orchestration, but does have some support for Windows, and DSC is for Windows Servers.

Both use YAML or similar structured config to impart a state, e.g.

- name: Install Firefox
  Ansible.builtin.package:
    name: firefox
    state: present

Meaning that ansible does the legwork to make sure FF is installed.

No, this is

• buying a surface from Microsoft
• immediately wiping it and installing Linux
• Microsoft then forcing you to authenticate using the device that is only tied to your account via purchase, and NOT login records, AND disabling other forms of auth