Run Anaconda dir/image installations only in non-interactive text mode
Anaconda will require a fully defined kickstart file for installations into an image or a directory and these installations will run only in a non-interactive text-based user interface.
- Name: Vendula Poncova
- Email: <firstname.lastname@example.org>
- Package: anaconda
- Name: Brian C. Lane
- Email: <email@example.com>
- Package: lorax (livemedia-creator)
- Targeted release: Fedora Linux 40
- Last updated: 2024-02-07
- Discussion thread
- FESCo issue: #3152
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
The Anaconda installer supports installations into a local image (via the
--image cmdline option) or a local directory (via the
--dirinstall cmdline option, the directory is usually a mount point of a custom image). These types of installations are supported by two user interfaces (text-based and GTK-based) in fully interactive, partially interactive and non-interactive modes. We believe that there is no strong reason for all these options, so we would like to minimize the scope of this functionality and support only the text-based non-interactive mode (specifically the command-line mode). It means that Anaconda will require a fully defined kickstart file and run only in the text-based user interface (during dir and image installations).
Benefit to Fedora
This is a preliminary step for an eventual deprecation and removal of the Anaconda support for dir and image installations. This functionality is being slowly taken over by Image Builder that is explicitly designed for building images and provides a much broader and better support for all kinds of images. Limiting the scope of dir and image installations in Anaconda will allow its developers to focus their resources on more prospective areas.
- Proposal owners: Will submit a pull request for
anacondato run dir and image installations only in the non-interactive text mode and update
livemedia-creatorto reflect these changes if necessary.
- Other developers: No impact.
- Release engineering: No impact. There should be zero impact on building official Fedora images since these processes are fully automated and use fully defined kickstart files. #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Community Initiatives:
How To Test
It will be still possible to use
livemedia-creator for installations into a local image or a directory with a fully defined kickstart file. Users can notice the following changes:
- If a user requests a dir or image installation, the installer runs in the text mode.
- If the user doesn't specify a kickstart file, the installer will report an error and abort.
- If the specified kickstart file is incomplete, the installer will report an error and abort.
- All options for specifying the user interface will be ignored (for example,
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
N/A (not a System Wide Change)