-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enlarge fedora VM starting disk #30
Conversation
d5f78b9
to
d8d4b06
Compare
@lsm5 PTAL when you get a sec. The commit message has more detail than the PR description 😉 |
@lsm5 un-poke. Should have run this through the podman tests first. There's some strange problem with the new images. |
note to me: https://cirrus-ci.com/task/6194088208760832 |
6ee092f
to
babc5a0
Compare
note to me: diskspace / cache problem is fixed:
|
Testing this in: containers/podman#8074 and containers/podman#8107 |
95399a1
to
248b9aa
Compare
This reverts commit f2ce736.
Previously python3 was installed by dependency resolution, but (somehow) this is no longer the case in F33. Install it explicitly. Also, install the /usr/bin/time command to help with simple resource-use monitoring at low-levels in automation scripts. Signed-off-by: Chris Evich <[email protected]> Install GNU time command Signed-off-by: Chris Evich <[email protected]>
Signed-off-by: Chris Evich <[email protected]>
Some users of the Fedora VM images need the ability to customize the disk partitioning/filesystem. Therefor the automatic disk-growing feature of cloud-init is deliberately disabled. At runtime, when the actual VM disk-size is known, a secondary post-boot process is used to manage partitions/filesystems. However, one particular podman testing job needs to make very heavy use of the Cirrus-CI build-caching system. Unfortunately the cache-management happens very early in the workflow, before any disk management scripts can execute. In order to accommodate both situations, the Fedora VM Image disk must be expanded the `base_image` stage. This allows automatic partition growth and filesystem resizing to occur during the `cache_image` build. Also, disable the automatic tmpfs mounting on /tmp. Include a comment referencing a bug with details about why the service cannot simply be disabled. Signed-off-by: Chris Evich <[email protected]>
248b9aa
to
ba96314
Compare
This is working now. |
@lsm5 PTAL, just is just for F33...an "accept" github review will cause this to merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
History dates back to PR containers#30, in 2020. Podman *really* needs /tmp to be tmpfs. Let's make it so. Signed-off-by: Ed Santiago <[email protected]>
History dates back to PR containers#30, in 2020. Podman *really* needs /tmp to be tmpfs. Let's make it so. All the /tmp->/var/tmp changes are because Rawhide build failed on reboot, because (duh) /tmp does not survive reboot Signed-off-by: Ed Santiago <[email protected]>
History dates back to PR containers#30, in 2020. Podman *really* needs /tmp to be tmpfs. Let's make it so. All the /tmp->/var/tmp changes are because Rawhide build failed on reboot, because (duh) /tmp does not survive reboot Signed-off-by: Ed Santiago <[email protected]>
History dates back to PR containers#30, in 2020. Podman *really* needs /tmp to be tmpfs. Let's make it so. All the /tmp->/var/tmp changes are because Rawhide build failed on reboot, because (duh) /tmp does not survive reboot Signed-off-by: Ed Santiago <[email protected]>
History dates back to PR containers#30, in 2020. Podman *really* needs /tmp to be tmpfs. Let's make it so. All the /tmp->/var/tmp changes are because Rawhide build failed on reboot, because (duh) /tmp does not survive reboot Signed-off-by: Ed Santiago <[email protected]>
History dates back to PR containers#30, in 2020. Podman *really* needs /tmp to be tmpfs. Let's make it so. All the /tmp->/var/tmp changes are because Rawhide build failed on reboot, because (duh) /tmp does not survive reboot Signed-off-by: Ed Santiago <[email protected]>
History dates back to PR containers#30, in 2020. Podman *really* needs /tmp to be tmpfs. Let's make it so. All the /tmp->/var/tmp changes are because Rawhide build failed on reboot, because (duh) /tmp does not survive reboot Signed-off-by: Ed Santiago <[email protected]>
History dates back to PR containers#30, in 2020. Podman *really* needs /tmp to be tmpfs. Let's make it so. All the /tmp->/var/tmp changes are because Rawhide build failed on reboot, because (duh) /tmp does not survive reboot Signed-off-by: Ed Santiago <[email protected]>
History dates back to PR containers#30, in 2020. Podman *really* needs /tmp to be tmpfs. Let's make it so. All the /tmp->/var/tmp changes are because Rawhide build failed on reboot, because (duh) /tmp does not survive reboot Signed-off-by: Ed Santiago <[email protected]>
Podman *really* needs /tmp to be tmpfs, to detect and handle reboots. Although there are (at this time) no reboots involved in CI testing, it's still important for CI hosts to reflect something close to a real-world environment. And, there is work underway to check /tmp: containers/podman#22141 This PR removes special-case Fedora code that was disabling a tmpfs /tmp mount. History dates back to PR containers#30 back in 2020. Some of the image-build code in this repo performs reboots and relies on persistent tmp files, so you'll note a flurry of /tmp -> /var/tmp changes. And, as a drive-by, document the Windows Chocolatey install command. Link to Best Practices, and explain why we disregard some of those. Signed-off-by: Ed Santiago <[email protected]>
Podman *really* needs /tmp to be tmpfs, to detect and handle reboots. Although there are (at this time) no reboots involved in CI testing, it's still important for CI hosts to reflect something close to a real-world environment. And, there is work underway to check /tmp: containers/podman#22141 This PR removes special-case Fedora code that was disabling a tmpfs /tmp mount. History dates back to PR containers#30 back in 2020. Some of the image-build code in this repo performs reboots and relies on persistent tmp files, so you'll note a flurry of /tmp -> /var/tmp changes. And, as a drive-by, document the Windows Chocolatey install command. Link to Best Practices, and explain why we disregard some of those. Signed-off-by: Ed Santiago <[email protected]>
Podman *really* needs /tmp to be tmpfs, to detect and handle reboots. Although there are (at this time) no reboots involved in CI testing, it's still important for CI hosts to reflect something close to a real-world environment. And, there is work underway to check /tmp: containers/podman#22141 This PR removes special-case Fedora code that was disabling a tmpfs /tmp mount. History dates back to PR containers#30 back in 2020. Some of the image-build code in this repo performs reboots and relies on persistent tmp files, so you'll note a flurry of /tmp -> /var/tmp changes. Signed-off-by: Ed Santiago <[email protected]>
Podman *really* needs /tmp to be tmpfs, to detect and handle reboots. Although there are (at this time) no reboots involved in CI testing, it's still important for CI hosts to reflect something close to a real-world environment. And, there is work underway to check /tmp: containers/podman#22141 This PR removes special-case Fedora code that was disabling a tmpfs /tmp mount. History dates back to PR containers#30 back in 2020. Some of the image-build code in this repo performs reboots and relies on persistent tmp files, so you'll note a flurry of /tmp -> /var/tmp changes. Signed-off-by: Ed Santiago <[email protected]>
Provide more disk space for podman's static-build task cache-restoration.