Humm… this seems rather strange. Maybe show us you docker-compose to have a look on how you configured immich’s network?
169.254.0.0/16 are APIPA addresses . So this a network misconfiguration.
After searching the web, I tried to create /etc/docker/daemon.json
This is not how you configure a docker network. This is only used if your local networks overlaps with docker’s defaut network.
The easiest way i can think on how to make your docker-compose work is to reinstall docker and use the host network. DO NOT forget to delete the /etc/docker/daemon.json file in case you want a fresh start. This seems a badly network configuration on you docker stack !
This will give you a good starting point! After that try to configure a bridge network for your docker compose.
Normally after you get the gist on how docker works, it’s rather easy!
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 !
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.
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 :)
after hours I tried to change distribution and went with fedora, set up everything, installed immich, not a single problem, it all works, also duckdns, and now I also have btrfs so I can snapshot my system. I’m probably very unlucky with debian based distributions, on my main laptop I had many problems with ubuntu as first distro, I had to distro hop a bit to find my place in EndeavourOS
thank you very very very very much for your time and help, I really appreciate this! now it’s time to actually start this journey in the magic world of self-hosting!
RHEL and other extremly long term support distros that have a significant user base because they hold back a lot of software features, network protocol features and moves to new dependencies that are required to work on the oldest and the newest supported distro for any given upstream software project.
Also, any time I have to learn something about a quirk in a version of software in use there it is basically wasted life time because the knowledge is already outdated by the time I obtain it.
I swear it is my machine or something, but despite CachyOS claiming being faster and more optimized I have yet to benchmark it as faster than the stock kernel for things I play around with. I wrote an application in rust to process a large text file and it both compiled and ran slower on CachyOS. I play around with llama.cpp and again it compiles and runs slower on CachyOS. I want to like Cachy, but right now all I can see is a bunch of window dressing to stock Arch with KDE and a couple of themes that I would rather change to default.
Also, why in the hell am I being asked to make a wifi password encryption key with the damn USB installer? CachyOS is not the only one. A lot of KDE using distros pop up the encryption window when you setup WiFi on the install image. Why? You want me to temporarily encrypt my wifi password on a temporary live image??? I just slows me down.
Anyways, I’m sure I’m crazy and clearly it is fast for somebody, but I can’t even get games to benchmark higher.
Did you test with different kernels? Them using a custom scheduler that prioritizes desktop applications might cause background things to run slower.
Plus, the use of ananicy (cpu/ram limiter) limits stuff like that as well.
I use cachyos because they set up zram, anf uksmd by defualt. That’s ram compression and deduplication, and it’a pretty powerful in my experience. If you’re using cachyos, then uksmdstats and zramctl can give you an idea of how much you are saving.
I used the default v3 kernel that Cachy installs by default. My guess is the workloads I have are Ram I/O bound and that just doesn’t mesh with the scheduler. I’m literally rooting for it to be faster because I want caring about scheduler and optimization to matter, but freaking stock Linux Mint ran the loads faster.
What is your actual personal use case, all you mention is a terminal, which every distro will support, likely with many different choices as to terminal options?
Beyond the usual browsing I’ll mainly be doing tinkering with hardware, gateware, firmware, CAD, art, projects that I may or may not finish, and the like. It’s going to be my “everything but playing video games” machine.
I’m assuming you’re running a Ryzen 7040 series then. No kernel support for the FPGA yet.
Honestly, I wasn’t aware that they had included a fabric. That’s really awesome, whether it is supported yet or not. I have a couple of dev boards and intend to build a board with a previous gen Xilinx chip that can fit in the expansion bay.
Also, Linux is great for gaming. Not sure why you’d limit yourself there.
100% agreed. However, I already have a Steam Deck and console, so, it’s more that gaming is already covered by other devices than thinking the system is not capable. I’m intending to take advantage of the modularity to turn the laptop into a platform more physically spacialized for tinkering.
Not quite your setup but I run Debian stable KDE with KVM.
I am also using distrobox to run applications in containers. It’s nice having arch/ubuntu/fedora/gentoo software running in a container and the application gets exposed to you stable environment. Another option is Bedrock Linux to look at
That’s absolutely my thought. Having a rock solid system close to the metal that doesn’t really get touched is something that I’ve become used to from work. It gives a lot more insurance against having to do as many re-installs and maximizes compatibility.
The UEFI firmware shouldn’t connect to the internet at all. You can’t rule it out entirely, but the threat is pretty small. Theoretically, it can access your hard drives, but again, it’s very unlikely that your BIOS will exfiltrate your data and send it somewhere. If you want to be sure, use LUKS for full disk encryption.
Konsole, but only because I’m on Plasma. I really don’t rven like it that much, but… well, it’s a terminal, it does terminal things so I’m more than OK with it.
On xfce, I would youse xfce-terminal.
anything is fine as long as basic stuff works - like ctrl/shift+insert (tho it’s a thing I had to manually setup in Konsole 😅)
I have had the exact same issue and I’ve been looking for a solution. If you really need the second monitor then you can just switch to the x11 session as a temporary fix but I have no idea what actually causes it.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.