ci: switch CGroup v1 test with VirtualBox#807
Merged
kenhys merged 2 commits intofluent:masterfrom Apr 8, 2025
Merged
Conversation
kenhys
force-pushed
the
ci-cgroupv1
branch
5 times, most recently
from
2e69ed0 to
dc26804
Compare
kenhys
changed the title
kenhys
force-pushed
the
ci-cgroupv1
branch
5 times, most recently
from
6732fd3 to
2b5086d
Compare
In the previous versions, AmazonLinux:2 image was lost from LXD, so switched from LXD to Incus. In this time, Ubuntu 20.04 runner will be removed from GitHub Actions, so need to give up using 20.04 runner for upcoming EOL (2025/04/15). Thus, there is no CGroup V1 host runner available on GitHub Actions. As a result, it means that there is no straightforward way to test package on CGroup v1 host. (such as AmazonLinux:2, AmazonLinux:2023) Instead, use vagrant (VirtualBox) to test fluent-package. It enables to run VM with CGroup v1 to keep CI alive. Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
kenhys
requested review from
Watson1978 and
daipom
and removed request for
Watson1978
Contributor
|
Note: We should unify |
kenhys
added a commit
to kenhys/fluent-package-builder
that referenced
this pull request
May 7, 2025
ci: switch CGroup v1 test on vagrant (VirtualBox) In the previous versions, AmazonLinux:2 image was lost from LXD, so switched from LXD to Incus. In this time, Ubuntu 20.04 runner will be removed from GitHub Actions, so need to give up using 20.04 runner for upcoming EOL (2025/04/15). Thus, there is no CGroup V1 host runner available on GitHub Actions. As a result, it means that there is no straightforward way to test package on CGroup v1 host. (such as AmazonLinux:2, AmazonLinux:2023) Instead, use vagrant (VirtualBox) to test fluent-package. It enables to run VM with CGroup v1 to keep CI alive. --------- Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
kenhys
added a commit
to kenhys/fluent-package-builder
that referenced
this pull request
May 7, 2025
ci: switch CGroup v1 test on vagrant (VirtualBox) In the previous versions, AmazonLinux:2 image was lost from LXD, so switched from LXD to Incus. In this time, Ubuntu 20.04 runner will be removed from GitHub Actions, so need to give up using 20.04 runner for upcoming EOL (2025/04/15). Thus, there is no CGroup V1 host runner available on GitHub Actions. As a result, it means that there is no straightforward way to test package on CGroup v1 host. (such as AmazonLinux:2, AmazonLinux:2023) Instead, use vagrant (VirtualBox) to test fluent-package. It enables to run VM with CGroup v1 to keep CI alive. --------- Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
kenhys
added a commit
to kenhys/fluent-package-builder
that referenced
this pull request
May 8, 2025
ci: switch CGroup v1 test on vagrant (VirtualBox) In the previous versions, AmazonLinux:2 image was lost from LXD, so switched from LXD to Incus. In this time, Ubuntu 20.04 runner will be removed from GitHub Actions, so need to give up using 20.04 runner for upcoming EOL (2025/04/15). Thus, there is no CGroup V1 host runner available on GitHub Actions. As a result, it means that there is no straightforward way to test package on CGroup v1 host. (such as AmazonLinux:2, AmazonLinux:2023) Instead, use vagrant (VirtualBox) to test fluent-package. It enables to run VM with CGroup v1 to keep CI alive. --------- Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
kenhys
added a commit
that referenced
this pull request
May 8, 2025
Backport #807 ci: switch CGroup v1 test on vagrant (VirtualBox) In the previous versions, AmazonLinux:2 image was lost from LXD, so switched from LXD to Incus. In this time, Ubuntu 20.04 runner will be removed from GitHub Actions, so need to give up using 20.04 runner for upcoming EOL (2025/04/15). Thus, there is no CGroup V1 host runner available on GitHub Actions. As a result, it means that there is no straightforward way to test package on CGroup v1 host. (such as AmazonLinux:2, AmazonLinux:2023) Instead, use vagrant (VirtualBox) to test fluent-package. It enables to run VM with CGroup v1 to keep CI alive. Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
kenhys
added
the
backported
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
ci: switch CGroup v1 test on vagrant (VirtualBox)
In the previous versions, AmazonLinux:2 image
was lost from LXD, so switched from LXD to Incus.
In this time, Ubuntu 20.04 runner will be removed from
GitHub Actions, so need to give up using 20.04 runner
for upcoming EOL (2025/04/15).
Thus, there is no CGroup V1 host runner available on GitHub Actions.
As a result, it means that there is no straightforward way to test package
on CGroup v1 host. (such as AmazonLinux:2, AmazonLinux:2023)
Instead, use vagrant (VirtualBox) to test fluent-package.
It enables to run VM with CGroup v1 to keep CI alive.