Re: rpm-ostree, dnf and bootc in a bootable containers world
On Tue, May 21, 2024 at 7:53 AM Stephen Smoogen wrote: > > > > On Tue, 21 May 2024 at 03:18, Petr Pisar wrote: >> >> V Mon, May 20, 2024 at 02:15:49PM -0400, Joseph Marrero napsal(a): >> > * dnf4 & dnf5 should provide a more helpful error when a user types >> > `dnf install` on a booted image-based system (pointing them to unlock >> > the system or use rpm-ostree). >> [...] >> > * dnf should be used during container builds of image-based Fedora for >> > most applications and examples. >> > >> How is it that DNF is not good enough for users, but at the same time it's >> good enough for building the images? >> > > My guess was that automatic builds will have an unlocked layer and failure to > have one means that something broke in the build system before then and needs > to be fixed. The error message wanted to be added would help the release > engineers also diagnose the problem and look for a fix. > > DNF does not understand image mode/ostree systems yet, however in a container build we are not in an ostree deployment which allows you to just run DNF or move files as needed. There is an effort to port the functionality from rpm-ostree to DNF but this will take time. -- Joseph Marrero -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
rpm-ostree, dnf and bootc in a bootable containers world
Greetings!
With all the updates that have happened with Ostree Native Containers
and Atomic desktops, we wanted to share some initial thoughts on the
direction for evolving the user experience of image-based systems and
what that means for the packages and projects that provide the
foundation for this technology.
The main tool to manage packages and upgrades on ostree systems has
been rpm-ostree. With the introduction of OSTree Native Containers and
CoreOS layering (https://github.com/coreos/layering-examples),
rpm-ostree turned into a system that also managed container-native
image upgrades and deployments. This gave us an opportunity to
reconsider `dnf` for image-based systems, a tool that Fedora system
administrators are accustomed to manage the RPM packages and introduce
`bootc`, a new tool to boot containers and manage image-based Fedora
deployments.
Rough consensus was forming around these points:
On the short-term:
* dnf4 & dnf5 should provide a more helpful error when a user types
`dnf install` on a booted image-based system (pointing them to unlock
the system or use rpm-ostree).
* `bootc` (https://github.com/containers/bootc) is now available to
manage the container/image-based lifecyle on Fedora 39 and up hosts.
* No new major development should be done on rpm-ostree; we will
provide fixes and security updates but major development for
client-side features should be directed to `bootc` for container/image
lifecycle management and `dnf` for package management.
* dnf should be used during container builds of image-based Fedora for
most applications and examples.
Long term (Maybe Fedora 43/45 timeframe...):
* rpm-ostree client-side functionality handling package
layering/install/overrides should be folded into dnf. (A *lot* of
details here)
* rpm-ostree will continue to be part of the ostree/ostree-container
base image composes. However this will be re-assessed after dnf has
become the default client-side tool for image-based Fedora systems.
As part of the UX we want dnf to continue to be the tool that
sysadmins see as the way to manage their RPM packages, even on
image-based systems. Some specific features of bootc to manage the
image lifecycle like `bootc upgrade` might be wrapped by `dnf upgrade`
on image mode systems, however we see bootc as the main tool to manage
the image-based hosts' deployments and we don't plan to hide this from
the customers behind dnf.
Our intent with the Fedora Change proposal is to cover the initial UX
changes, add bootc and and re-introduce dnf on image-mode variants.
The new proposal builds on top of functionality added on these
previous enhancements:
* OstreeNativeContainer:
https://fedoraproject.org/wiki/Changes/OstreeNativeContainer
* OstreeNativeContainerStable:
https://fedoraproject.org/wiki/Changes/OstreeNativeContainerStable
If you would like to share feedback you can reach out to us via the
methods outlined at
https://docs.fedoraproject.org/en-US/bootc/community/ and you can
follow the new change proposal here:
https://fedoraproject.org/wiki/Changes/DNFAndBootcInImageModeFedora
Signed off by:
- David Cantrell
- Jonathan Lebon
- Colin Walters
- Timothée Ravier
- Joseph Marrero
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
OSTree Native Containers layering examples
Greetings! I wanted to share with our Fedora devel community that the CoreOS layering-examples have matured enough for versioning the repo. At the moment we have 11 examples showing how to create a OCI compliant images that then you can boot into with the features added as part of: https://fedoraproject.org/wiki/Changes/OstreeNativeContainer The release is located at the following link: https://github.com/coreos/layering-examples/releases/tag/v2022.1 All the examples use Fedora CoreOS as their base image, however they should work with any OSTree Native Container that has a recent rpm-ostree version. We don't have an official Kinoite or Silverblue oci container yet but Colin Walters has a pretty cool build here: https://github.com/cgwalters/sync-fedora-ostree-containers We are excited about the possibilities this enables for our users and community and even more excited about seeing people already playing with it. Check out this video by Jorge Castro: https://www.youtube.com/watch?v=X8h304Jp9N8 which shows part of what is possible in action. As we move towards stabilizing these features as part of: https://fedoraproject.org/wiki/Changes/OstreeNativeContainerStable We look forward to your contributions and comments. -- Joseph Marrero ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 proposal: Replace DNF with DNF5 (System-Wide Change proposal)
+1 on this, I was wondering if there are any plans to include rpm-ostree in this effort? rpm-ostree today uses libdnf and since fedora silverblue & fedora coreos are managed by rpm-ostree it would be nice to have an unified plan/coordination for this change. Furthermore, it would also be nice if we could provide a more unified user experience in the Fedora distributions universe. -- Joseph Marrero ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
future contributions and package updates jmarrero
Hello, My FAS is : jmarrero I can not update any of my packages for the time being, will know If I can continue contributing in about a month. I can pass the ownership to who ever wants to maintain the packages I currently own or we can share ownerships if I can still contributing. But will not know my status until august 1st is my best guess. The packages I maintain are: Fedora: homerun mirall qtkeychain owncloud-csync rosa-launcher Fedora and Epel: php-channel-aws php-aws-sdk php-channel-sabredav php-sabredav-Sabre php-sabredav-Sabre_DAVACL php-sabredav-Sabre_DAV php-sabredav-Sabre_HTTP php-sabredav-Sabre_VObject php-sabredav-Sabre_CardDAV php-sabredav-Sabre_CalDAV I am very sorry for any inconvenience this may cause, specially near the F21 Freeze. -- Joseph Marrero -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Retina 13 Macbook pro and fedora19
Fedora 19 boots ok and the installer opens, but as soon The installation starts and Anaconda tries to mount the efi partition it crashes. Saying the efi partition can not be mounted. I selected automatic partitions and it created / /home /boot and /boot/efi I deleted /home and left / /boot /boot/efipartitions In Fedora 18 the installation is OK. I created the USB-bootable drive using dd if=~/Fedora-Live-KDE-x86_64-19-Alpha-1.iso of=/dev/disk1 under OS X for both f18 and f19. -- Joseph Marrero -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fwd: [mirall] plasma client try3
From: Joseph Marrero jmarr...@gmail.com
Date: Wed, Mar 6, 2013 at 11:40 PM
Subject: Re: [mirall] plasma client try3
To: Kevin Fenzi ke...@scrye.com
I am preparing the package for upstream merge between mirall and
owncloud-plasma-client
This is are test builds, they are not going to be pushed to any kind of
updates until the official builds have been merged together
the issue with the lib is resolved in the current upstream but in the
owncloud-plasma-client is not.
Let me know if I should not make it build to test in the f19 repos.
On Wed, Mar 6, 2013 at 11:33 PM, Kevin Fenzi ke...@scrye.com wrote:
On Wed, 6 Mar 2013 01:00:26 + (UTC)
Joseph Marrero jmarr...@fedoraproject.org wrote:
commit 868b82191f2627c6f34d64abb554b06e53de41fb
Author: Joseph Marrero jmarr...@fedoraproject.org
Date: Tue Mar 5 20:59:46 2013 -0400
plasma client try3
mirall.spec |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
---
diff --git a/mirall.spec b/mirall.spec
index 3ef7fd5..9a0bb17 100644
--- a/mirall.spec
+++ b/mirall.spec
@@ -97,7 +97,8 @@ fi
#remove libmirallsync on official merge
%{_libdir}/libmirallsync.so
%{_libdir}/libowncloudsync.so
-
+##for some reason this is unlinked in this mirall pull, in the
uptream version is working +/usr/lib/libowncloudsync.so
# re activate when officially merged#%{_libdir}/libowncloudsync.so.0
#%{_libdir}/libowncloudsync.so.%{version}
What are you trying to do here?
The x86_64 version of this package shouldn't ship any libraries
in /usr/lib/
Is this some issue with upstreams make install?
Why not manually install it in the right place?
kevin
--
Joseph Marrero
--
Joseph Marrero
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Self Introduction
Hello My name is Joseph Marrero from Isabela, Puerto Rico. I am a computer Science Student, currently in last semester to finish my bachelor degree. I have been using Linux since 2000, started in Mandrake 7.2 and ended in Red Hat Linux 7.1 where my RedHat/Fedora love affair started. I have used Gentoo/Arch for a while and helped a little with KDE in a local Linux distribution called VidaLinux around 2008. Using linux made me very passionate in computers specially software. In 2006 started working in Computer Stores and since 2010 I work as an IT Administrator in a local GPS Tracking Company. I migrated their Windows Server to linux. I do all computer stuffs there from giving support to clients to setting up all the OpenGTS/LAMP servers. I am looking forward to do packaging for fedora specially for KDE related stuff. This is the package I am currently working on: https://bugzilla.redhat.com/show_bug.cgi?id=846850 All my Computer Science homework and programs can be browsed here: https://docs.google.com/folder/d/0B0IbyJGzQiLLS0dia2tiSzlKRlk/edit have a great day :) -- Joseph Marrero -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
