blog.wyrihaximus.net/2024/10/building-secure-images-with-github-actions

Preview meta tags from the blog.wyrihaximus.net website.

Linked Hostnames

12

Search Engine Appearance

Google

https://blog.wyrihaximus.net/2024/10/building-secure-images-with-github-actions

Building Secure Images with GitHub Actions

When I initially started building Docker images only amd64 was relevant, and having a build ⇒ Scan ⇒ Test ⇒ Push cycle was as easy as using docker save and docker load. But with arm64 becoming more and more popular, including with my own home cluster, I needed to add images for arm64. For a while this meant I was pushing images with -amd64 and -arm64 suffixes before combining them into one “image”. All because I want to ensure no images with CVE’s or bugs are pushed. Skipping those is not acceptable for me as a Software Engineer. Photo by Pixabay



Bing

Building Secure Images with GitHub Actions

https://blog.wyrihaximus.net/2024/10/building-secure-images-with-github-actions

When I initially started building Docker images only amd64 was relevant, and having a build ⇒ Scan ⇒ Test ⇒ Push cycle was as easy as using docker save and docker load. But with arm64 becoming more and more popular, including with my own home cluster, I needed to add images for arm64. For a while this meant I was pushing images with -amd64 and -arm64 suffixes before combining them into one “image”. All because I want to ensure no images with CVE’s or bugs are pushed. Skipping those is not acceptable for me as a Software Engineer. Photo by Pixabay



DuckDuckGo

https://blog.wyrihaximus.net/2024/10/building-secure-images-with-github-actions

Building Secure Images with GitHub Actions

When I initially started building Docker images only amd64 was relevant, and having a build ⇒ Scan ⇒ Test ⇒ Push cycle was as easy as using docker save and docker load. But with arm64 becoming more and more popular, including with my own home cluster, I needed to add images for arm64. For a while this meant I was pushing images with -amd64 and -arm64 suffixes before combining them into one “image”. All because I want to ensure no images with CVE’s or bugs are pushed. Skipping those is not acceptable for me as a Software Engineer. Photo by Pixabay

  • General Meta Tags

    17
    • title
      Building Secure Images with GitHub Actions — Cees-Jan Kiewiet's blog
    • charset
      utf-8
    • theme-color
      #1abc9c
    • viewport
      width=device-width, initial-scale=1.0
    • X-UA-Compatible
      IE=edge

  • Twitter Meta Tags

    6
    • twitter:card
      summary_large_image
    • twitter:image:src
      https://blog.wyrihaximus.net/images/posts/building-secure-images-with-github-actions_big.jpg
    • twitter:site
      @WyriHaximus
    • twitter:title
      Building Secure Images with GitHub Actions
    • twitter:description
      When I initially started building Docker images only amd64 was relevant, and having a build ⇒ Scan ⇒ Test ⇒ Push cycle was as easy as using docker save and docker load. But with arm64 becoming more and more popular, including with my own home cluster, I needed to add images for arm64. For a while this meant I was pushing images with -amd64 and -arm64 suffixes before combining them into one “image”. All because I want to ensure no images with CVE’s or bugs are pushed. Skipping those is not acceptable for me as a Software Engineer. Photo by Pixabay

  • Link Tags

    23
    • alternate
      https://blog.wyrihaximus.net/atom.xml
    • apple-touch-icon
      /images/jackson/76x76.png
    • apple-touch-icon
      /images/jackson/120x120.png
    • apple-touch-icon
      /images/jackson/128x128.png
    • apple-touch-icon
      /images/jackson/152x152.png

Links

30