Update Fedora Atomic from 27 to 28 #206
Closed
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.
Fedora Atomic 2018-04-25 releaseTesting
Controller instances sometimes fail AWS network reachability checks after running for a whileKickstart installs to disk fail during storage configuration preparing the/mnt/sysimage/boot
bind mountrepo
on an older system (Fedora 25 in my case). Preparing therepo
withrpm-ostree-2018.4-1.fc28.src.rpm
solved the sysimage mount issue.Note, Typhoon for Fedora Atomic is still alpha. It doesn't receive the same burn-in/simmer testing and production usage as Container Linux yet.