new image: gomplate

[sanjayk0508]

New Image Pull Request Template

Related: #2497

• The Image is smaller in size than its common public counterpart.
• The Image is larger in size than its common public counterpart (please explain in the notes).

Notes:

Image Vulnerabilities

• The Grype vulnerability scan returned 0 CVE(s).
• The Grype vulnerability scan returned > 0 CVE(s) (please explain in the notes).

Notes:

Image Tagging

• The image is not tagged with version tags.
• The image is tagged with :latest
• The image is not tagged with :latest (please explain in the notes).

Notes:

Basic Testing - K8s cluster

• The container image was successfully loaded into a kind cluster.
• The container image could not be loaded into a kind cluster (please explain in the notes).

Notes:

Basic Testing - Package/Application

• The application is accessible to the user/cluster/etc. after start-up.
• The application is not accessible to the user/cluster/etc. after start-up. (please explain in the notes).

Notes:

Helm

• A Helm chart has been provided and the container image can be used with the chart. If needed, please add a -compat package to close any gaps with the public helm chart.
• A Helm chart has been provided and the container image is not working with the chart (please explain in the notes).
• A Helm chart was not provided.

Notes:

Processor Architectures

• The image was built and tested for x86_64.
• The image could not be built for x86_64 (please explain in the notes).
• The image was built and tested for aarch64.
• The image could not be built for aarch64. (please explain in the notes).

Notes:

Functional Testing + Documentation

• Functional tests have been included and the tests are passing. All tests have been documnted in the notes section.

Notes:

Environment Testing + Documentation

• There has not been a request and/or there is no indication that this image needs tested on a public cloud provider.
• The container image has been tested successfully on a public cloud provider (AWS, GCP, Azure).
• The container image has not been tested successfully on a public cloud provider (AWS, GCP, Azure) (please explain in the notes).

Notes:

Version

• The package version is the latest version of the package. The latest tag points to this version.
• The package version is the not the latest version of the package (please explain in the notes).

Notes:

Dev Tag Availability

• There is a dev tag available that includes a shell and apk tools (by depending on 'wolfi-base')
• There is not a dev tag available that includes a shell and apk tools (by depending on 'wolfi-base') (please explain in the notes).

Notes:

Access Control + Authentication

• The image runs as nonroot and GID/UID are set to 65532 or upstream default
• Alternatively the username and GID/UID may be a commonly used one from the ecosystem e.g: postgres
• The image requires a non-standard username or non-standard GID/UID (please explain in the notes).

ENTRYPOINT

• applications/servers/utilities set to call main program with no arguments e.g. [redis-server]
• applications/servers/utilities not set to call main program with no arguments e.g. [redis-server] (please explain in the notes)
• base images leave empty.
• base image and not empty (please explain in the notes).
• dev variants is set to entrypoint script that falls back to system.
• dev variants is not set to entrypoint script that falls back to system (please explain in the notes).

CMD

• For server applications give arguments to start in daemon mode (may be empty)
• For utilities/tooling bring up help e.g. –help
• For base images with a shell, call it e.g. [/bin/sh]

Environment Variables

• Environment variables added.
• Environment variables not added and not required.

SIGTERM

• The image responds to SIGTERM (e.g., docker kill $(docker run -d --rm cgr.dev/chainguard/nginx))

Logs

• Error logs write to stderr and normal logs to stdout. Logs DO NOT write to file.

Documentation - README

• A README file has been provided and it follows the README template.

[sanjayk0508]

Error

terraform apply
var.target_repository
  The docker repo into which the image and attestations should be published.

  Enter a value: cgr.dev/chainguard/gomplate

module.latest-config.data.apko_config.this: Reading...
module.latest-config.data.apko_config.this: Still reading... [10s elapsed]

Planning failed. Terraform encountered an error while generating this plan.

╷
│ Error: computing package locks
│
│   with module.latest-config.data.apko_config.this,
│   on config/main.tf line 12, in data "apko_config" "this":
│   12: data "apko_config" "this" {
│
│ resolving apk packages: for arch "loong64": error getting repository indexes: reading index
│ https://packages.wolfi.dev/os/loongarch64/APKINDEX.tar.gz: fetching https://packages.wolfi.dev/os/loongarch64/APKINDEX.tar.gz:  
│ GET https://packages.wolfi.dev/os/loongarch64/APKINDEX.tar.gz (Range: bytes=0-): unexpected status code: 404
│ for arch "s390x": error getting repository indexes: reading index https://packages.wolfi.dev/os/s390x/APKINDEX.tar.gz: fetching 
│ https://packages.wolfi.dev/os/s390x/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/s390x/APKINDEX.tar.gz (Range: bytes=0-): 
│ unexpected status code: 404
│ for arch "386": error getting repository indexes: reading index https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz: fetching     
│ https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz (Range: bytes=0-):     
│ unexpected status code: 404
│ for arch "riscv64": error getting repository indexes: reading index https://packages.wolfi.dev/os/riscv64/APKINDEX.tar.gz:      
│ fetching https://packages.wolfi.dev/os/riscv64/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/riscv64/APKINDEX.tar.gz       
│ (Range: bytes=0-): unexpected status code: 404
│ for arch "arm/v7": error getting repository indexes: reading index https://packages.wolfi.dev/os/armv7/APKINDEX.tar.gz:
│ fetching https://packages.wolfi.dev/os/armv7/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/armv7/APKINDEX.tar.gz (Range:   
│ bytes=0-): unexpected status code: 404
│ for arch "ppc64le": error getting repository indexes: reading index https://packages.wolfi.dev/os/ppc64le/APKINDEX.tar.gz:      
│ fetching https://packages.wolfi.dev/os/ppc64le/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/ppc64le/APKINDEX.tar.gz       
│ (Range: bytes=0-): unexpected status code: 404
│ for arch "arm/v6": error getting repository indexes: reading index https://packages.wolfi.dev/os/armhf/APKINDEX.tar.gz:
│ fetching https://packages.wolfi.dev/os/armhf/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/armhf/APKINDEX.tar.gz (Range:   
│ bytes=0-): unexpected status code: 404
│ for arch "amd64": getting indexes for "386" sibling: reading index https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz: fetching  
│ https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz (Range: bytes=0-):     
│ unexpected status code: 404
│ for arch "arm64": getting indexes for "386" sibling: reading index https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz: fetching  
│ https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz (Range: bytes=0-):     
│ unexpected status code: 404
╵
╷
│ Error: Invalid function argument
│
│   on ../../tflib/publisher/chainguard.tf line 43, in resource "chainguard_image_repo" "repo":
│   43:   readme    = file(local.readme_filepath)
│     ├────────────────
│     │ while calling file(path)
│     │ local.readme_filepath is "images/./README.md"
│
│ Invalid value for "path" parameter: no file exists at "images/./README.md"; this function works only with files that are        
│ distributed as part of the configuration source code, so if this file will be created by a resource in this configuration you   
│ must instead obtain this result from an attribute of that resource.

Error details

1. Package Resolution Errors

The error message mentions that Terraform is unable to fetch the APKINDEX files for various architectures from the specified URLs, resulting in 404 errors.

unexpected status code: 404

2. Invalid File Path for README

This error relates to an invalid file path:

Invalid value for "path" parameter: no file exists at "images/./README.md"

Please take a look and let me know how I should approach the issue!