i have to shamly say i had to give up atomics system as my main developement and study setup since i ust ouldent get everything working on it not even on container setup and this was huge for me since i have been using long time atomics and usually can get everyhting workarounded, but not anymore.
even layered VScode and 1password and 1password-cli issues kept coming. tryied sysext apps on some, but main issues came to get 1password.agent to connect on toolbox containers so couldent get pull/push/commits signed.
tested distrobox where it actually sees agent, but then it fails to connect to GitHub API same as toolbox, but then i can sign in as local server, but still missing agent.sock to sing everyhting.
will test later again when new release comes, but as in years using it feels it is actually getting harder and harder to get atomic as developer platform espeially if using ssh,gpg password managers to sign and connect to everyhting
yeah for me as software developer student i see how good atomic can be and how powerfull it can be especially with containers and secure core system. Just need to do more work on it and it will be so good, but for now i need to use mutable fedora
security is there and easy containers, no dependency hell, keep your syustem minimal and clean. Spin container setup what you need - do your stuff and delete container. isolated enviroments worry free updates and minimal risk of esaped malicious pakages etc
1password is only one i use sine i can add serets and keeps secrets, sign commits all need to be authentiate and i have been using it for years and wont change.
Maybe i just need to create custom image
adding vscode, 1password, 1password-cli, nordvpn, distrobox on main image. Bootc FDE etc just could solve the issues for me
Containers are just as easy in a standard Fedora install though? To me that’s the best combination, a standard base system and using containers for transient applications like development work.
Since Atomic Desktops will eventually transition to bootable containers, I would encourage you to at least give it a try if you haven’t already. I have been using a custom Fedora Silverblue bootable container image as a daily driver for quite some time now and I can try to assist you build it and switch to one. It can be built locally, so it doesn’t necessarily need to be pushed to a remote repository or registry, but you do need to build and maintain it.
just grabbed ublue starter template and cheking it out and figuring how stuff is done. i think i am going to try and make it work for my workflow, but i think i might want still use fedora base more
I really appreciate the great work that the folks at the Universal Blue project are doing. I’m not very familiar with the template and won’t be able to help much with it. If you decide to try Fedora Silverblue as well, we can try to build an image with the applications you want.
On the other hand, if the issue is only with 1password, perhaps building a custom image with this single application will be enough. At least this will be a good starting point for learning.
kinoite is my main and as reading more and more about bootc fedora seems good choise for that.
the issue is not fully on 1 app it is multiple clusters realted to 1 app. the app it self works, but main issue comes more on the apps what i need and use all together.
my workflow what i prefer to use always is vscode to containers. 1password/1password-cli for ssh keys, secrets, gpg, signing, commits and vpn for privacy etc
main issue is that i try to not layer since that is what basically kills atomic on my mind and layer if i really need.
for my layered apps are vscode, 1password, 1password-cli, nvidia drivers
sysext apps opnH264, nordvpn, steam controller support
rest are flatpaks
container podman/toolbox
the issue comes when i connect VScode to toolbox container since somehow it is ROOT user there only on VScode and there it cant see 1password Agent.sock or cli so i cant commit, push, pull, git so basically all workflow is dead. i tested on Distrobox sysext and there no issues on that side since vscode is same user as host, but issues there comes getting timeout error from GitHub API so again no workflow there too.
getting bootc and no rpm-ostree sounds like a fix for everyhting
If you need NVIDIA on Atomic Desktops or Bootable Containers, my personal recommendation would be to use or derive from one of the images provided by the Universal Blue project.
I would recommend experimenting and testing with bootable containers. This way, you not only contribute to the Fedora and Universal Blue projects, but you also learn new technologies that will eventually be implemented.
so building custom image from ublue is the way to go. need to start learning and setting it up then. i could still make all the same stuff using fedora without all ublue prebuilds and setup it corretly so automated all and updates just works
Since you have NVIDIA, i think it will be easier to start with an image that already has drivers included. Then, when you gain some experience, you can try building your own images from Fedora Atomic Desktops bootable containers, like Universal Blue’s.
