```
git clone <aports repo>.git # Only needed once obviously
cd aports
[cd <pakage subdir]
[TARGET_ARCH='x864_64']package_builder_alpine.sh [/bin/sh]
```
And that's it. The bringup-teardown of the container take a little time, so you can launch a shell instead, and call `package_builder_alpine.sh` within the shell.
The script will generate (temporary) keys if it cannot find them in the mounted volumes.
But even this can take some time, and so after running it once, to generate the keys etc, one can then just use the standard abuild tools, to make debugging faster.
In a second editor, on the local host, one can use any OS as per normal, e.g. git, vi, etc.
Not sure what the persistent storage requirement is about, but what I do, after installing my tool https://gitlab.com/esbs/package_builder-alpine/
``` git clone <aports repo>.git # Only needed once obviously cd aports [cd <pakage subdir] [TARGET_ARCH='x864_64']package_builder_alpine.sh [/bin/sh] ```
And that's it. The bringup-teardown of the container take a little time, so you can launch a shell instead, and call `package_builder_alpine.sh` within the shell.
The script will generate (temporary) keys if it cannot find them in the mounted volumes.
But even this can take some time, and so after running it once, to generate the keys etc, one can then just use the standard abuild tools, to make debugging faster.
In a second editor, on the local host, one can use any OS as per normal, e.g. git, vi, etc.