https://github.com/evancarroll/alpine-packaging-image
An image building script to ease packaging for Alpine.
https://github.com/evancarroll/alpine-packaging-image
alpine alpine-linux buildah containerization packaging packaging-tool
Last synced: 3 months ago
JSON representation
An image building script to ease packaging for Alpine.
- Host: GitHub
- URL: https://github.com/evancarroll/alpine-packaging-image
- Owner: EvanCarroll
- Created: 2021-02-20T01:22:34.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2021-02-20T07:39:27.000Z (over 4 years ago)
- Last Synced: 2025-07-21T18:31:04.458Z (3 months ago)
- Topics: alpine, alpine-linux, buildah, containerization, packaging, packaging-tool
- Language: Shell
- Homepage:
- Size: 3.91 KB
- Stars: 2
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Alpine Image Builder for Packaging
=====
This is a simply a container meant to be run rootless to ease alpine package
creation. It installs the tools needed, and pulls down the alpine [`abuild`
repo](https://github.com/alpinelinux/abuild).
This is pretty simple,
* Edit the `/.env` file
* Run `rootless.sh` to create the rootless container
* Run `run.sh` to jump into it and [get to packaging!](https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package#Creating_an_APKBUILD_file)
How does it work?
=====
When you're packaging you can mutilate an entire system trying different
things. Containers are great for "restoring" state without messing up your
machine. You can be totally careless with them, destroy and recreate them.
This repository pulls down `abuild` repository linked above. That's where your
build files like the `APKBUILD` reside (the Alpine equivalent of RHEL Spec
files). This gets volume mounted into the container with the `run.sh` script.
It's the only state that remains from one iteration of `run.sh` to another.
Notes on Root (UID=0)
=====
Many of the [Alpine build utilities will error if you try to run them as root](https://unix.stackexchange.com/q/635291/3285). **This error is safe to
ignore!** as none of the utilities actually run as root with this
configuration. When logged into a rootless container you have uid=0 from the
perspective of the container, but you're actually mapped back to the user that
executed `podman run`. Some of the utilities will require a capital `-F` flag
to force them to permit root. This is fine.