Talk:Alpine Package Keeper

note on apk update

There is an --update-cache or -U option which can be used together with apk <anything> that will first perform an apk update. Might be worth mentioning that. --Ncopa 11:02, 16 August 2010 (UTC)

There is an --initdb option that does not even show in apk help command. Is this deprecated ? --Vkrishn (talk) 10:32, 2 May 2013 (UTC)

"Packages and Repositories" section - ftp still being used?

The stated section currently has the following example of a valid repo:

ftp://dl-3.alpinelinux.org/alpine/v2.6/main

Is the ftp protocol still being used? The passage could then be updated to "v3.7". --John3-16 (talk) 22:43, 19 January 2018 (UTC)

Troubleshooting - "apk-tools is old"

Could the following instruction be added? This may not yet have been tested on a system that is still exhibiting this error message:

If edge is not tagged, upgrade from one of the edge/main mirrors. For example:

sudo apk add --upgrade apk-tools --update-cache --repository http://dl-2.alpinelinux.org/alpine/edge/main/ --allow-untrusted

--John3-16 (talk) 04:58, 1 February 2018 (UTC)

How to use the --virtual parameter

As a new user trying to keep a docker image small but needing to compile some packages, it would be very, very helpful to include a detailed explanation of the `--virtual` parameter of `add` with examples of how to use it. I would add it myself but I only know what I've read in stackoverflow and, well, you know how reliable that can be… TIA

— Preceding unsigned comment added by Tedsecretsource (talk • contribs) 08:45, 22 January 2023‎

.boot_repository in package cache

It seems like the advice about using .boot_repository with the cache directory doesn't work, since a repository requires an APKINDEX.tar.gz file but the cache has APKINDEX.f00bar.tar.gz files. Should the article be changed, or is this a bug? Dklr433 (talk) 20:01, 4 March 2024 (UTC)

Repository pinning

I found the below section in a older version of this page. But after reading the manual, i believe the information is wrong. The current content appears as tagged repository. Can someone please confirm, if my understanding/changes are correct.

---

You can specify additional "tagged" repositories

Contents of /etc/apk/repositories

... @personal https:/personal-repo.example.com/alpine-apks/

After which you can "pin" dependencies to these tags using: apk add application@personal apk will by default only use the untagged repositories, but adding a package with a @tag: 1. will prefer the repository with that tag for the named package, even if a later version of the package is available in another repository 2. allows pulling in dependencies for the tagged package from the tagged repository (though it prefers to use untagged repositories to satisfy dependencies if possible)

---

Prabuanand (talk) 05:32, 24 March 2025 (UTC)