Alpine in PRoot
#1
Tue, 2017-07-25 13:32
tpimh
-
- Offline
- 8 months 1 week ago
- 2017-07-25
I'm trying to install Alpine in PRoot (in order to get it working with no superuser privileges).
Here are the commands:
$ mkdir alpine $ cp apk.static alpine $ ./proot -S alpine /apk.static -X <a href="http://dl-cdn.alpinelinux.org/alpine/edge/main" rel="nofollow">http://dl-cdn.alpinelinux.org/alpine/edge/main</a> -U --allow-untrusted --initdb add alpine-base fetch <a href="http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz " rel="nofollow">http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz </a>(1/16) Installing musl (1.1.16-r15) (2/16) Installing busybox (1.27.0-r2) Executing busybox-1.27.0-r2.post-install ERROR: busybox-1.27.0-r2.post-install: script exited with error 127 (3/16) Installing alpine-baselayout (3.0.4-r0) Executing alpine-baselayout-3.0.4-r0.pre-install ERROR: alpine-baselayout-3.0.4-r0.pre-install: script exited with error 127 Executing alpine-baselayout-3.0.4-r0.post-install ERROR: alpine-baselayout-3.0.4-r0.post-install: script exited with error 127 (4/16) Installing openrc (0.24.1-r2) Executing openrc-0.24.1-r2.post-install ERROR: openrc-0.24.1-r2.post-install: script exited with error 127 (5/16) Installing alpine-conf (3.6.0-r0) (6/16) Installing libressl2.5-libcrypto (2.5.5-r0) (7/16) Installing libressl2.5-libssl (2.5.5-r0) (8/16) Installing zlib (1.2.11-r0) (9/16) Installing apk-tools (2.7.2-r0) (10/16) Installing busybox-suid (1.27.0-r2) (11/16) Installing busybox-initscripts (3.1-r1) Executing busybox-initscripts-3.1-r1.post-install ERROR: busybox-initscripts-3.1-r1.post-install: script exited with error 127 (12/16) Installing scanelf (1.2.2-r0) (13/16) Installing musl-utils (1.1.16-r15) (14/16) Installing libc-utils (0.7.1-r0) (15/16) Installing alpine-keys (2.1-r1) (16/16) Installing alpine-base (3.6.0-r0) Executing busybox-1.27.0-r2.trigger ERROR: busybox-1.27.0-r2.trigger: script exited with error 127 4 errors; 6 MiB in 16 packages
4 errors in scripts. The scripts look okay and I can run them. I don't know why does it fail. How can I debug the installation? I've been trying rebuilding the packages adding "set -x" to the scripts, but I couldn't install my versions because of signature problems. And I doubt that it will help because the scripts probably just fail to run. Is there a simpler way to debug it? It runs okay with root privileges.