So I got it up and running in 10 minutes just by copy/pasting the docker-compose.yaml and .env files. So their configuration files are working flawlessly.
Either you have a router misconfiguration or a docker network misconfiguration. Either way If I were you I would first start without duckdns.org domain name and without to much complex network configuration. Start slow and build up to more complex configurations.
Leave your router defaults network configuration, without any open ports.
See if your spare laptop server has internet access when everything is defaulted (if not that’s the first thing to solve)
Check if your networks configuration is in the inet 172.17.0.1/16 brd 172.17.255.255 range (dockers default bridge network)
Default routes on your laptop
DHCP or manual
The important part is to make your laptop have internet access without changing to much, the default DHCP works great !
Fresh docker installation and don’t forget to delete your json file (/etc/docker/daemon.json)
Try again with the docker-compose.yaml and .env from immich’s github
If your network configuration is wrong from the beginning, you are in for bad times specially if you are going to use duckdns ! Try to make it work on your local network first and than you can go crazy.
Also if you do not know what you are doing, please don’t make your containers accessible to the web ! Rather use a wireguard server to access all your containers from everywhere in the world with a secure tunnel !
If you’re a beginner, there is alot to grasp before having a good working laptop server :)