You might need to figure out errors and install dependencies. Then build it as packager in the same directory as the APKBUILD file: su - packager You need to be not root user so create a packager user with password: adduser -D packager & addgroup packager abuild Install the build tools: apk -U add alpine-sdk Then choose a commit for your APKBUILD file and download it. Steps:Ĭlick on the commit, click on the APKBUILD file links and "Log" on the menu to get the commit log of the APKBUILD file. The complete Alpine Linux organisations repositories can be found on this self hosted GitLab instance.īecause I was using the testing repo. The official recommendation is to keep your own mirror / repository with all the specific package and their versions that you may want to use. There has been discussion of keep all packages tagged as Alpine in the future. Thus we currently keep only the latest for each stable branch, and has always been like that. We don't at the moment have resources to store all built packages indefinitely in our infra. The official recommendation can be read here, citation below.Īlternately, you could simply set a minimum package version instead of an exact version. Pinning a package to an exact version carries the risk that the package will be dropped from the repo, and your Dockerfile will fail to build in the future. (At /packages, click "edge" and change it to the alpine image version you use, and click "search" again.) Never pin packages from the "edge" branch of the alpine package repo, as these are in test and may be revoked. The package repository can be found here: In case you can't find a package, while you can see it in the UI for Alpine packages, update your sources/package database: apk update You can set "sticky" versions like this: # Both are equal
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |