Was working today on kind of an entry piece for Community Design Team: a logo and new mascot for #Bootc (special type of container).
His name is Bootseef and he's ready to fly through updates! 🚀🚀 Thanks to Madeline Peck and Design Team for the sketches, sources and color choices that inspired me. 👋 I enjoyed doing this particular mascot the most.
@fedora.design@peertube.linuxrocks.online and #CommunityDesignTeam have lots of work on their plate, so I invite aspiring and designers by trade to have a looksie-look in their GitLab issues. @fedora has engineering and other teams worth their gold, making software great, as well.
Something strange happened to me today. A developer reached out because after restarting some #docker containers, nginx seemed to be behaving oddly. I connected and realized something big was off. It appeared to be a different container, bloated, and nginx wasn't even starting. After ruling out the possibility of the nginx image from the docker registry being compromised, we started to brainstorm. Long story short, another developer had created a custom image and named it "nginx," so the dockerfile was pulling it directly from the local setup... #DockerTroubles#Linux#Containers
docker-compose is great, but I love using @fedora CoreOS lately and I want to use the built-in tools it provides. I also want automatic updates without a privileged watchtower container running.
Hello Fediverse! I'm Jake, a Software Engineer that likes building cool, impactful things! I've written mostly JavaScript and TypeScript in my career and love #containers, #kubernetes, and #nix / #nixos.
Containers are a big part of how uBlue and atomic systems work. Let your OS install be a stable host and use containers to cleanly tinker or manage applications no matter what distro it's packaged for.
🐘 Exciting times ahead! Just wrapped up speaking at NDC Sydney about 'Containerizing .NET' and can't wait to bring the conversation to Orlando Code Camp this week. 🚀 Delving into .NET in a box, my latest blog post explores the ins and outs of containerizing .NET, sharing insights and learnings from the journey. Whether you're deep in the .NET world or curious about containerization, check it out! 📖➡️ https://chris-ayers.com/2024/2/19/containerizing-dotnet-part-2#dotnet#containers#devcommunity
We have byte-by-byte reproducible builds of everything at Polar Signals, including container images. We just migrated from podman to buildkit, and it looks like producing provenance information includes build times, ultimately breaking reproducibility. Is there any way to fix this?
If you use Fedora Atomic Desktops or Fedora CoreOS, this may be a neat account to follow as it's what we use to manage containers - an important part of how to use this kind of system.
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.