Uploaded image for project: 'Insights Experiences'
  1. Insights Experiences
  2. HMS-9242

Migrate service AMI builds from quay.io/app-sre/packer:latest to our own container

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Image Builder
    • None
    • Migrate service AMI builds from quay.io/app-sre/packer:latest to our own container
    • Done
    • image-builder-1
    • 0% To Do, 0% In Progress, 100% Done
    • False

      Background

      In Image Builder, we use the quay.io/app-sre/packer:latest container to build AMIs that we then run in our service. We have been experiencing Packer failures when installing the latest releases of the packer-plugin-amazon plugin. But the problem seems to be the version of Packer installed in the container (see https://github.com/hashicorp/packer-plugin-amazon/issues/598 and https://discuss.hashicorp.com/t/important-update-official-packer-plugin-distribution-moving-to-releases-hashicorp-com/75972). The container uses Packer v1.8.0 , we would need v1.14.0.

      It turns out that AppSRE does not have the capacity to update the container image, and we are the only users of it.

      Therefore, the idea is to build our own UBI-based container image using Packer and utilize it for creating our service AMIs.

      Slack discussion: https://redhat-internal.slack.com/archives/CCRND57FW/p1756804633214869

      Acceptance criteria

      • The distribution/Dockerfile-ubi-packer container file in the osbuild-composer repository does not use quay.io/app-sre/packer:latest.
      • Packer builds in the osbuild-composer repository CI pipeline are finished successfully.

       

       

              thozza@redhat.com Tomas Hozza
              thozza@redhat.com Tomas Hozza
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: