mirror: switch default policy to OFFLINE_INSTALL by default #1971
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dbungert
approved these changes
Apr 12, 2024
|
@d-loose FYI this will change the default behavior on desktop too. Subiquity will automatically switch to a semi-offline installation if the mirror connectivity test fails. |
Automated installations and desktop installations will now switch to an offline installation by default. In this mode, only packages from the pool will be fetched. This should allow the installation to proceed when installing from a private network without external access to the internet. Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com>
ogayot
force-pushed
the
fallback-offline-install-by-default
branch
from
f399231 to
01338fa
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automated installations and desktop installations will now switch to an offline installation by default. In this mode, only packages from the pool will be fetched.
This should allow the installation to proceed when installing from a private network without external access to the internet.
This is similar in essence to #1816 but applies the policy to automated server installs as well.
If you are doing a desktop installation (or an automated server installation) in a private network with no Internet access, the mirror connectivity test will eventually timeout and the installer will switch to an "offline" installation. (let's call it semi-offline).
Going forward, I think we should have a new directive in autoinstall configuration mimicking
use_during_installationfrom #1968, so that users can do a semi-offline installation without going through the mirror connectivity test at all.