• 1 Post
  • 16 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle








  • i don’t understand how i connect the pc to the domain.

    Yeah, that’s the part where I think there’s some misunderstanding. You don’t “connect” the server to your domain. Instead, there is a Nameserver (most run by your registrar, GoDaddy) that hosts a list of DNS records, that you can edit, which point to IPs. So you need to edit those to point to your public IP (or set up stuff like DynDNS if your IP isn’t static) and once that’s doneand the port forwarding is also set up properly in the Fritz!Box you should be able to connect.

    That said, what’s wrong with VPN? Particularly if you’re using Wireguard VPN, which was recently added to Fritz!Box, there shouldn’t be any performance differences. Plus, it would be safer than exposing services to the whole internet, doubly so if you’re not a networking expert.





  • From my experience the “default” experience, which is Docker Desktop, is a pain, due to what you described. In particular, Linux containers and Windows file permissions just don’t mix well.

    Other than that, there’s three options:

    1. Docker Desktop, but used from WSL 2. This seems to be the cleanest solution nowadays. Never personally used it though. Officially supported.
    2. Installing Docker inside WSL 2. Configuring this correctly is a bit of a pain and not really supported AFAIK.
    3. Installing Docker in a VM, using the integrated Hyper-V functionality for example. The least amount of integration, but most reliable.

  • It doesn’t make any sense to me from the perspective that I’ve approached it.

    I think you’ve already identified the issue. Docker is pretty “simple”, but you’ve got to approach it from the right angle or else it doesn’t make sense. Apart from suggesting the official documentation I can’t give you much advice on how to learn it because my path to understanding Docker was pretty much just trying things out and iterating on it. That said here’s a tips that could help:

    • If you aren’t using Docker Compose already, you really should. Just having your entire configuration for a service in a single file really helps.
    • Aside from debugging, you normally aren’t meant to run commands manually in a container. It’s best to act like every container is just a black box that simply does its thing.
    • If you need to edit config files, the easiest way is to just directly on the host if you’re using bind mount volumes, or spin up a temporary container running Debian or Alpine for example that also has the Docker Volume mounted.

    As @housepanther@lemmy.goblackcat.com has already mentioned, building your own images is also pretty helpful since it strips a lot of the “black magic” away and teaches you how to further “mod” existing images.


  • I’d guess that it might be related to how you’ve set up the virtual network adapter. This depends on the specifc virtualization software you use, but the adapter for HA should be be set to something called bridged network, meaning the VM gets its own IP on your home network, no routing or NAT in between. HA will struggle to connect with devices otherwise, as all these protocols weren’t designed to work across multiple networks.



  • If you need something that packs more power than a Pi while still being somewhat energy efficient and small form factor then yes, the NUCs are generally pretty good.

    Personally I’m running a NUC from 2018 with a 8th gen i3 that’s pulling double duty as both a server running about ~10 docker containers, and as a media center.

    The server part still runs flawlessly, though the media center part is getting a bit slow when opening websites on it.

    As others have already said, one drawback is that there’s only space for one drive, so at least a NAS or external USB storage is recommended for backups.