Mamy tu jakiś speców od Dockera?
Próbuję skonfigurować dockera używając podmana i udało mi się uruchomić kontener i podpiąć katalog z hosta do kontenera, ale sieci nie ogarniam.
Kontener jest uruchomiony na zwyklym uzytkowniku na serwerze. Działa dostęp do DNS i webowki z laptopa, ale z androida juz nie i nie mam pojecia co jest. Jak zmieniam dns na telefonie, to wifi krzyczy, ze niema neta.
Ta adresacja takze jest dla mnie jakas dziwna. LAN ma adresacje 192.168.X.X, a kontener ma siec 10.X.X.X.
Juz chyba wszystkiego probowalem. Wylaczylem firewalla na serwerze i chyba wszystko co blokuje reklamy na androidzie, ale nadal dupa.
Jakby kogos interesowalo, to probuje skonfigurowac "Technitium DNS Server"
#Podman v5.0.0 has been released! It’s the first major release in 2 years and includes several new features & significant changes:
➡️ a complete rewrite of the podman machine command to improve hypervisor support on macOS and Windows
➡️ supports OCI artifacts in manifest files,
➡️ adopts Pasta by default for rootless networking,
➡️ and more.
The next Podman Community Cabal meeting is happening in two weeks, on Tuesday, May 21, 2024, at 11:00am EDT (UTC-5). Currently no topics, so if you want to discuss something, please add it to the agenda! https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg?both#opensource#podman
#Podman has been ported to #FreeBSD. And it can run Arch Linux for me.
Linux containers in FreeBSD can start through the old good #Linuxulator - which does not support complex features like cgroups or namespaces, which means I probably can't run a container inside a container. Yet.
But this Linux layer is actively supported in FreeBSD for almost 20 years and is rock-solid! It started in 2006 at Google, based on Linux kernel 2.6 and today it shows up as 5.15-compatible!
Buah-eh... until the TypeScript ran the way I had to have it for WebComponents it had taken me forever to search for libraries and I hadn't even started writing the code tests yet… 🤦♂️🤷♂️
Been battling to get #LaravelSail working with rootless #Podman all evening and aren't having much luck. Boo to overly complex things.
It's so close to working well but the whole uid/gid mapping thing just falls apart when the container starts running things as different users. All of a sudden there're large parts of my source tree that I can't edit, not to mention being unable to use artisan make tools.
The Forgejo community has just published the 7.0.1 bug fix release[1]. I went to my server, did a systemctl stop forgejo, to stop the rootless container[2] I use to run it, issued podman pull codeberg.org/forgejo/forgejo:7-rootless to get the updates, and finally systemctl start forgejo and done. Updated. Thank you @forgejo for being awesome and working so hard on making things better and better!
debugging between podman's container / quadlet file with systemd is kinda tricky, especially when there is a typo in the container file, there is not warning or error i can find from journalctl. took me a whole day + night to realized that 1 single typo. the parser is just too graceful... #podman#systemd
"IPAM error: failed to find free IP in range: 10.89.0.1 - 10.89.0.254"
/run/user/1000/netns contains 257 netns-* files.
The thing is: ip netns list shows nothing, and podman network rm does not fix the issue. Rebooting probably will, but that's the Windows way of solving things …
Anyone running #PaperlessNGX#rootless using #Podman and #PodmanCompose under #Debian12? The volumes I'm mapping to the host always get chowned to 100999:100999, and that's with USERMAP_UID=1000 and USERMAP_GID=1000 in docker-compose.env.
Playing around with PODMAN_USERNS mainly leads to the container not starting at all (in at least one case because it can't install packages).
a) Set USERMAP_UID=0 and USERMAP_GID=0. Paperless will run as root inside of the container, which maps to your user's UID on the host. Some parts of #PaperlessNGX (e.g. Celery) might warn about running as root, but they don't refuse doing it.
b) Set USERMAP_UID=1000 and USERMAP_GID=1000 (or whatever they are on your host), add "user: 0" to each of the services in docker-compose.yml, start with PODMAN_USERNS=keep-id podman-compose up.
Did you miss the Podman Community Cabal meeting this week? No worries, the video is now up on YouTube! We talked about data production appliances and backups, encapsulation, and a bit more. #opensource#podmanhttps://youtu.be/aLKET_3loWw
I, again, am thinking about combining Silverblue as my base system with a more complex Nix setup to replace toolbox (which is effectively a separate whole Linux to maintain or throw away regularly, or build a CI for to create new images, etc. -- nah).
Now, Nix works fine, but it needs to store things under /nix because most binaries are prefix dependent and not portable in their location. But what if I download the nix store to $HOME/.nix instead and then launch a light-weight throw-away container/namespace that simply maps $HOME/.nix to /nix but keeps everything else identical?
Would that work? Did someone already build that stuff?