-
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
Add support for building AWS EC2 AMIs #132
Conversation
Cirrus CI build successful. Image ID |
Cirrus CI build successful. Image ID |
9b81859
to
6c5f1c5
Compare
Cirrus CI build successful. Image ID |
d12bead
to
5f1a9a3
Compare
Cirrus CI build successful. Image ID |
025a9a9
to
d1d0df1
Compare
Cirrus CI build successful. Image ID |
cec8f78
to
8403259
Compare
8ce9dfb
to
755ffc6
Compare
Cirrus CI build successful. Image ID |
fda863c
to
d27ff2c
Compare
Cirrus CI build successful. Image ID |
* Update the Containerfile comment for accuracy. * Simplify package installation script. * Distinguish certain tasks as container or VM-only during setup. Signed-off-by: Chris Evich <[email protected]>
Certain podman and aardvark-dns CI testing requires capabilities not available in GCE. Respectively, executing on bare-metal and on the arm64 architecture. * Add the necessary `Makefile` targets, packer definitions, script, and CI updates to produce AWS images. * Add the `gvproxy` package to Fedora images to support testing the `podman-machine` command. * Increase the build timeout since AWS is considerably slower and more failure-prone than GCE. * Update documentation to reflect how both GCE and EC2 images are built. Signed-off-by: Chris Evich <[email protected]>
@edsantiago @baude @lsm5 PTAL (I know it's a lot). I'd like to get this in today or early tomorrow since I'll be on PTO next week. Hopefully I've not made too many egregious gaffs 😕 |
This is a flake (likely bug in the Ubuntu 2204 repositories):
I'll re-run the |
Re: failing ubuntu repos. I opened #143 in case it becomes a problem, it will provide a way to easily bypass that build. |
Note to me: Latest podman image |
Cirrus CI build successful. Image ID |
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, in my limited experience 😐
Thanks for taking a look @lsm5 I know it's a lot 😞 I'm just going to merge this then. Any problems can be addressed in future PRs. |
Certain podman and aardvark-dns CI testing requires capabilities
not available in GCE. Respectively, executing on bare-metal and on the
arm64 architecture.
Makefile
targets, packer definitions, script,and CI updates to produce AWS images.
gvproxy
package to Fedora images to support testing thepodman-machine
command.failure-prone than GCE.
N/B: It was decided that AWS functionality in CI is urgently needed. While PR is possibly at the "good enough" stage for merging, there are some significant TODO's introduced:
...
menu for each file.fedora-aws Cache Image
andfedora-netavark-aws Cache Image
. These need to be manually extracted from the output logs (ormanifest.json
artifact). The image ID posted by github-actions bot only applies to GCE images.m5zn.metal
instances - they cost $4/hour to leave running.