The whole promise of #containers and #snap is that applications just work in the sandbox. And then that:
/snap/obsidian/28/app/obsidian: /snap/core20/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /lib/x86_64-linux-gnu/libcups.so.2)
Są tu spece od Dockera? Próbuję uruchomić kontener Dockera używają Podmana (https://github.com/TechnitiumSoftware/DnsServer/blob/master/CHANGELOG.md), ale utknąłem. Po wielu próbach, kombinowaniu, aktualizacji setek programów, utknąłem na niemożności uruchomienia kontenera, bo twierdzi, że port 53/tcp jest w użyciu. Zrobiłęm już chyba wszystko, co mi wpadło do głowy, czyli wyłączenie systemd, wyłączenie nasłuchiwania przez systemd na porcie 53 i nic to nie daje. Co ciekawe, netstat nie pokazuje portu 53 jakoby był w użyciu, więc nie wiem nawet, jaki program może tego używać. Co ciekawe, jak wziąłem nmapa z innego hosta, to pokazuje, ze port 53 jest zamkniety, wiec cos tam nasluchuje, ale nie wiem co.
Podobno podman używa jakiegoś własnego serwera DNS do zarządzania siecią między kontenerami, ale nie ogarniam tego, a i nie wiem, czy tu może być problem. Poza tym serwerem podmana, nie przychodzi mi juz nic do glowy.
@centopus@linux_pl
Ja miałem taką sytuację, że kiedyś instałowałem drivery do dwóch urządzeń. drivery do jednego urządzenia chodziły na kernelu nie nowszym niż XXX, a drugie urządzenie było dość nowe, więc sterowniki były w kernelu, ale jednym z nowszych, więc miałem zabawę w szukanie kernela, który będzie działał z oboma urządzeniami.
Co do dnsmasq, to ważne, że już działa. Martwi mnie tylko ta zwiecha. Kiedyś mi się takie coś wydarzyło, jak byłem poza domem 3 tygodnie i przeszło 2 tygodnie nie miałem dostępu do serwera.
Here's a Flatpak story: The other day, my best friend told me that he had switched to Linux! Arch Linux with KDE Plasma, a noble choice in my opinion. He's a smart guy, but he was having some issues that he couldn't figure out: Firefox' maximise and minimise buttons were missing, drag and drop from archives wasn't working, his selected theme wasn't applied everywhere, and many other small issues I can't remember now.
I tried reproducing his issues on my machine, but everything worked fine for me. We were confused. Is there missing libraries? We went through packages to find out what my system had that his didn't. It was weird, everything was kinda working, but the devil was always in the details, for every single app.
And then we found it: All those applications he had issues with were Flatpaks! He simply didn't pay attention when installing them through the Discover store. He didn't even know what Flatpak meant.
I helped him remove Flatpak from his system and install the system packages instead, and all issues were gone.
Man, Flatpaks suck. How does anyone prefer Flatpaks over system packages? How does anyone think this was a good idea? Stop trying to invent new things to solve old problems and instead go back and fix the problems.
Containers, Flatpak, Immutable distros, it's all wasted effort. There is no magical solution that will solve all our problems. The only way to solve all problems is by solving each problem individually one by one. And that is exactly what countless distribution and package maintainers are doing on your behalf every single day.
@fell You completely miss the point of Flaptaks and immutable systems (which you kinda already use if you have iOS or Android installed on your phone) because you didn't take the time to learn about why you can't just "fix the old problems".
@element For the sake of this discussion I glanced over the Arch Wiki page about Flatpak again. Specifically the troubleshooting section.
"There is no ideal way to apply system themes in flatpak apps"
"There is no single standard to set the cursor properly."
I find this unacceptable. The response to "Flatpak is not the future" is only giving me more reasons to avoid Flatpak, as it fails to defend the original arguments.
However, I do believe Flatpak can be a great way of distributing software, if - and only if - all apps and system components are Flatpaks. But at this point you might as well consider Flatpak it's own Linux distribution.
To me, the only use of Flatpak in its current state is more like an emulator. It's not really emulating anything, but it enables some applications to run that wouldn't otherwise run on the system, which is a common use case of emulators.