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 :)
First find out what’s your debian network configuration if it’s a fresh install and everything is installed by default, you get your ip and network from DHCP
<span style="color:#323232;">> ip a
</span>
If your ethernet or wifi networks is in the inet 172.17.0.1/16 brd 172.17.255.255 range it overlaps with the default docker bridge network.
Nah, that’s not how it works ! I have over 10 applications and half of them have databases, and that’s the prime objective of containers ! Less resource intensive and easier to deploy on low end machines. If I had to deploy 10 VMs for my 10 applications, my computer would not be able to handle it !
I have no idea how it works underneath, that’s a more technical question on how container engines work. But if you searx it or ask chatGPT (if you use this kind of tool) i’m sure you will find out how it works :).
Immich isn’t the easiest docker stack ! I will up it on my own server and give you some feedback.
Because their isn’t any network configuration in the compose it uses the default docker network. Thus… maybe… it overlaps with your own network, that’s what your first post was about :)
I will look into it and if nobody comes up with an anwser before me, will give you some feedback on how it went and try to find out what’s wrong !
Hey, could you elaborate or send some lecture? I have the upstream quad9 DoH address in adguard. It’s supposed to better encrypt my traffic right? Never saw any ads or strange DNS requests.
Never heard about ads being inject though DoH or DoT, or did I misunderstood your comment?