Wolfi
Create a Wolfi registry, generate an identity token, then publish and install private Wolfi Linux packages with apk using the --allow-untrusted flag.
Use a Wolfi registry to host private Wolfi Linux packages. Self-published indexes are unsigned, so apk commands against this registry require the --allow-untrusted flag unless you configure a signing key.
What you will learn from this topic
In this quickstart, you will:
Create a registry in Harness Artifacts.
Publish a package to the registry.
Install the package from the registry, and confirm that it works.
Before you begin
Install Alpine Package Keeper (
apk) on your local machine.Install
curl. You use it to publish packages to your registry.Make sure you have access to a Harness account with permission to create registries and connectors.
Create a Wolfi Registry
To create a Wolfi Registry, perform the following steps:
In Artifact Registry, select Registries.
Select + Create Registry.
Specify the Registry name.
Optionally, add a Description.
Choose visibility between Public and Private. The default is Private.
Select Wolfi as the Registry type.
Click Save.
Select Create to finalize.
Upstream proxy configuration (optional)
An upstream proxy allows your registry to fetch Wolfi packages from an external source when they are not available locally. The default upstream is the Wolfi OS package repository, https://packages.wolfi.dev/os.
Create upstream proxy
To create an upstream proxy, perform the following steps:
In Artifact Registry, select Registries.
Select the drop-down next to + Create Registry and select Upstream Proxy.
Specify the Registry name.
Optionally, add a Description.
Choose visibility between Public and Private. The default is Private.
Select Wolfi as the Registry type.
Select the Source: Wolfi Linux or Custom.
If you select Custom, specify the Remote registry URL.
Select the Authentication method. The default is Anonymous for the public Wolfi Linux mirror.
Username and password: Specify the username and password. Use an existing secret, or create a new secret by specifying the Name and entering the Secret text.
Anonymous: No credentials required.
Select Create to finalize.
Configure the upstream proxy in your registry
To configure the upstream proxy in your registry, perform the following steps:
In Artifact Registry, select an existing Wolfi Artifact.
Go to the Configuration tab.
Select Edit in the Upstream proxy section.
Click + Add upstream proxy.
Select the required proxy from the list.
Click Apply.
Select Update to finalize.
Wolfi client setup
In your Wolfi Artifact, select Set Up Client. The dialog gives you an identity token, then setup instructions for apk.
Generate an identity token
An identity token serves as the password for authenticating with the registry.
In your Wolfi Artifact, select Set Up Client.
Select Generate Token.
Select an Expiration for the token:
30 Days
90 Days
180 Days
Custom
Copy the token. You use it in the following steps in place of
<IDENTITY_TOKEN>.
Configure the client
Configure apk to use the registry, then publish and install packages. Replace the values in angle brackets with your own values.
1. Configure the apk repository
Add the registry to /etc/apk/repositories:
URL-encode the @ in your email address as %40.
Refresh the index (allow untrusted indexes):
2. Publish a package
Upload a built .apk file to the registry. The .PKGINFO inside the package supplies the package name, version, and architecture:
3. Install a package
Install the package with apk:
Setup verification
Confirm that your registry serves the package you published. To verify your setup, perform the following steps:
On a host with no cached index for this registry, run
apk update --allow-untrusted, then install the package you published withapk add --allow-untrusted <ARTIFACT_NAME>=<VERSION>.Confirm that
apkdownloaded the package from your Harness registry address, which is shown in Set Up Client.In Harness, open your registry and confirm that the package and version appear in the package list.
If a step fails, go to Troubleshooting to resolve common authentication and resolution issues before you retry.
Pipeline automation (optional)
Publishing from a pipeline gives you a repeatable release process. Run the publish step when you create a version tag, so each release maps to one version in the registry.
The following Run step publishes a built .apk file with the version tag embedded in the filename. Store the identity token as a Harness secret, and do not write it into the pipeline YAML.
Troubleshooting
Next steps
To add a pipeline that publishes a new version for every release tag, go to Harness CI.
To control who can publish and consume packages in your registry, go to RBAC and permissions.
To set retention and lifecycle rules for old versions, go to Lifecycle Management overview.
Last updated
Was this helpful?