aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2021-08-31T21:48:01Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12406ERROR: busybox-1.32.1-r2.trigger: script exited with error 1 on alpine:3.13.12021-08-31T21:48:01ZFabian NeugartERROR: busybox-1.32.1-r2.trigger: script exited with error 1 on alpine:3.13.1Hey!
I'm trying to build a docker image for armv7 with [GitHub actions](https://github.com/neugartf/mautrix-telegram/actions/runs/546400737/workflow) from `alpine:3.13.1`, which fails with the following error:
```
#5 21.67 (148/148) Inst...Hey!
I'm trying to build a docker image for armv7 with [GitHub actions](https://github.com/neugartf/mautrix-telegram/actions/runs/546400737/workflow) from `alpine:3.13.1`, which fails with the following error:
```
#5 21.67 (148/148) Installing yq (3.4.1-r0)
#5 22.02 Executing busybox-1.32.1-r2.trigger
#5 22.02 ERROR: busybox-1.32.1-r2.trigger: script exited with error 1
#5 22.02 Executing ca-certificates-20191127-r5.trigger
#5 22.04 /bin/sh: can't open 'trigger': No such file or directory
#5 22.04 ERROR: ca-certificates-20191127-r5.trigger: script exited with error 2
#5 22.06 1 error; 227 MiB in 162 packages
#5 ERROR: executor failed running [/dev/.buildkit_qemu_emulator /bin/sh -c apk add --no-cache python3 py3-pip py3-setuptools py3-wheel py3-virtualenv py3-pillow py3-aiohttp py3-magic py3-sqlalchemy py3-telethon-session-sqlalchemy py3-alembic py3-psycopg2 py3-ruamel.yaml py3-commonmark py3-idna py3-decorator py3-tqdm py3-requests py3-numpy py3-pysocks py3-cffi py3-qrcode py3-brotli ffmpeg ca-certificates su-exec netcat-openbsd olm-dev py3-pycryptodome py3-unpaddedbase64 py3-future bash curl jq yq]: exit code: 1
```
<p>
<details>
<summary>Dockerfile</summary>
<pre><code>FROM alpine:3.13.1
RUN apk add --no-cache \
python3 py3-pip py3-setuptools py3-wheel \
py3-virtualenv \
py3-pillow \
py3-aiohttp \
py3-magic \
py3-sqlalchemy \
py3-telethon-session-sqlalchemy \
py3-alembic \
py3-psycopg2 \
py3-ruamel.yaml \
py3-commonmark \
# Indirect dependencies
py3-idna \
#moviepy
py3-decorator \
py3-tqdm \
py3-requests \
#imageio
py3-numpy \
#py3-telethon@edge \ (outdated)
# Optional for socks proxies
py3-pysocks \
# cryptg
py3-cffi \
py3-qrcode \
py3-brotli \
# Other dependencies
ffmpeg \
ca-certificates \
su-exec \
netcat-openbsd \
# encryption
olm-dev \
py3-pycryptodome \
py3-unpaddedbase64 \
py3-future \
bash \
curl \
jq \
yq
COPY requirements.txt /opt/mautrix-telegram/requirements.txt
COPY optional-requirements.txt /opt/mautrix-telegram/optional-requirements.txt
WORKDIR /opt/mautrix-telegram
RUN apk add --virtual .build-deps \
python3-dev \
libffi-dev \
build-base \
&& sed -Ei 's/psycopg2-binary.+//' optional-requirements.txt \
&& pip3 install -r requirements.txt -r optional-requirements.txt \
&& apk del .build-deps
COPY . /opt/mautrix-telegram
RUN apk add git && pip3 install .[speedups,hq_thumbnails,metrics,e2be] && apk del git \
# This doesn't make the image smaller, but it's needed so that the `version` command works properly
&& cp mautrix_telegram/example-config.yaml . && rm -rf mautrix_telegram
VOLUME /data
ENV UID=1337 GID=1337 \
FFMPEG_BINARY=/usr/bin/ffmpeg
CMD ["/opt/mautrix-telegram/docker-run.sh"]</code></pre>
</details>
</p>
Any ideas how to fix this?
Thanks!https://gitlab.alpinelinux.org/alpine/aports/-/issues/12113Dependencies on gammu component broken: Cannot delete SMS messages2020-11-17T16:37:42ZOscar CalvoDependencies on gammu component broken: Cannot delete SMS messagesA [gammu issue](https://github.com/gammu/gammu/issues/460) is preventing dependencies to delete SMS messages.
This [has been fixed](https://wammu.eu/news/2020/10/03/gammu-1-42-0/), however we need to release a bug fix release of Alpine s...A [gammu issue](https://github.com/gammu/gammu/issues/460) is preventing dependencies to delete SMS messages.
This [has been fixed](https://wammu.eu/news/2020/10/03/gammu-1-42-0/), however we need to release a bug fix release of Alpine so that it can be consumed by [Home Assistant](https://github.com/home-assistant/core/issues/40462).Scrumpy JackScrumpy Jackhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12110wkhtmltopdf segfaults2021-08-07T16:59:34ZPaul Zillmannwkhtmltopdf segfaultsThe package `wkhtmltopdf` segfaults at about 30 to 40% of it's progress.
This is reproducible with the 3.12 repo and the edge repo.
Example call: `wkhtmltopdf https://google.com /tmp/google.pdf`The package `wkhtmltopdf` segfaults at about 30 to 40% of it's progress.
This is reproducible with the 3.12 repo and the edge repo.
Example call: `wkhtmltopdf https://google.com /tmp/google.pdf`Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/7946nss-pam-ldapd missing libnss_ldap.so.22020-10-23T08:58:45Zalgitbotnss-pam-ldapd missing libnss_ldap.so.2After installing and configuring nss-pam-ldapd I get the following error
when starting the nslcd service:
nslcd: Warning: NSS\_LDAP module not loaded: Error loading shared
library libnss\_ldap.so.2: No such file or directory
*(from re...After installing and configuring nss-pam-ldapd I get the following error
when starting the nslcd service:
nslcd: Warning: NSS\_LDAP module not loaded: Error loading shared
library libnss\_ldap.so.2: No such file or directory
*(from redmine: issue id 7946, created on 2017-09-29)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/6710Package request: nss_wrapper2022-09-21T11:16:54ZDennis SchriddePackage request: nss_wrapperPlease package nss\_wrapper: https://cwrap.org/nss\_wrapper.html
It is a small library that allows to fake NSS passwd and group
information, by filling a custom passwd file with “fake” information
that is used by programs started with L...Please package nss\_wrapper: https://cwrap.org/nss\_wrapper.html
It is a small library that allows to fake NSS passwd and group
information, by filling a custom passwd file with “fake” information
that is used by programs started with LD\_PRELOADing nss\_wrapper.
This is especially useful inside a container, where information about
the executing user might not be available in /etc/passwd, because it was
specified on the Docker command-line using the —user argument. In such
situation it is necessary to create a custom passwd file containing
information about this user, since some programs require this to work
properly.
*(from redmine: issue id 6710, created on 2017-01-20)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/11522ImageMagick number of supported formats: 02020-11-06T07:58:42ZjuliemarsImageMagick number of supported formats: 0Hi
I hope this is the right place, I discovered this issue in the linuxserver letsencrypt docker image (https://github.com/linuxserver/docker-letsencrypt/issues/445) and they suggested I post it to you.
Expected Behavior
The ImageMagi...Hi
I hope this is the right place, I discovered this issue in the linuxserver letsencrypt docker image (https://github.com/linuxserver/docker-letsencrypt/issues/445) and they suggested I post it to you.
Expected Behavior
The ImageMagick module is not working, in phpinfo I can see that it says "ImageMagick number of supported formats: 0" this is preventing some functions needing this library from working.
If I disable the ImageMagick.ini file the system falls back to GD and works fine.
Nothing is logged in the docker or NGINX/php log for this error either.
I have deleted and recreated the container and image and tried on 2 different docker installs and issue remains on both.
Current Behavior
Images do not load generating a 500 error.
![image](/uploads/f18596106a3b0e3e49c193f07fc3036a/image.png)
Steps to Reproduce
Setup new image
Use ImageMagick module (webtress uses this)
See 500 error/no image (webtress logs Cannot create thumbnail NoDecodeDelegateForThisImageFormat `PNG'"
they have advised the following:
"We have this php module installed: https://pkgs.alpinelinux.org/package/v3.11/community/x86_64/php7-pecl-imagick
It pulls in the imagemagick-libs: https://pkgs.alpinelinux.org/package/v3.11/community/x86_64/imagemagick-libs
That's why php is listing the imagemagick library version. But no idea why it's not finding any supported formats."
Any ideas?Andy PostnikovAndy Postnikovhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/10627clang requires a few gcc libraries, which supposed to be privided by compiler-rt2021-01-29T01:16:23ZTrevis Schifferclang requires a few gcc libraries, which supposed to be privided by compiler-rtHello, I noticed something strange.
Some of the crt files should come from compiler-crt, but these ones come
with gcc:
crtprec32.o
crtendS.o
crtbeginS.o
crtfastmath.o
crtprec64.o
crtbeginT.o
crtprec80.o
...Hello, I noticed something strange.
Some of the crt files should come from compiler-crt, but these ones come
with gcc:
crtprec32.o
crtendS.o
crtbeginS.o
crtfastmath.o
crtprec64.o
crtbeginT.o
crtprec80.o
crtbegin.o
crtend.o
Above libs are not usable without gcc libs (Thus I guess GPL is still
enforced?).
b17wise@eula47 /tmp % clang Hello.c -o hello -fuse-ld=/usr/bin/ld.lld
ld.lld: error: cannot open crtbeginS.o: No such file or directory
ld.lld: error: unable to find library -lgcc
ld.lld: error: unable to find library -lgcc_s
ld.lld: error: unable to find library -lgcc
ld.lld: error: unable to find library -lgcc_s
ld.lld: error: cannot open crtendS.o: No such file or directory
clang-8: error: linker command failed with exit code 1 (use -v to see invocation)
b17wise@eula47 /tmp % sudo apk add gcc
[sudo] password for b17wise:
(1/8) Installing binutils (2.32-r0)
(2/8) Installing isl (0.18-r0)
(3/8) Installing libgomp (8.3.0-r0)
(4/8) Installing libatomic (8.3.0-r0)
(5/8) Installing mpfr3 (3.1.5-r1)
(6/8) Installing mpc1 (1.1.0-r0)
(7/8) Installing gcc (8.3.0-r0)
(8/8) Installing gcc-zsh-completion (5.7.1-r0)
Executing busybox-1.30.1-r2.trigger
OK: 2012 MiB in 482 packages
b17wise@eula47 /tmp % clang Hello.c -o hello -fuse-ld=/usr/bin/ld.lld
b17wise@eula47 /tmp % ./hello
Hello, Alpine
b17wise@eula47 /tmp % apk info -L gcc | grep -e *crtendS*
b17wise@eula47 /tmp % apk info -L gcc | grep crt
usr/lib/gcc/x86_64-alpine-linux-musl/8.3.0/crtbegin.o
usr/lib/gcc/x86_64-alpine-linux-musl/8.3.0/crtend.o
usr/lib/gcc/x86_64-alpine-linux-musl/8.3.0/crtbeginT.o
usr/lib/gcc/x86_64-alpine-linux-musl/8.3.0/crtbeginS.o
usr/lib/gcc/x86_64-alpine-linux-musl/8.3.0/crtprec32.o
usr/lib/gcc/x86_64-alpine-linux-musl/8.3.0/crtprec80.o
usr/lib/gcc/x86_64-alpine-linux-musl/8.3.0/crtprec64.o
usr/lib/gcc/x86_64-alpine-linux-musl/8.3.0/crtendS.o
usr/lib/gcc/x86_64-alpine-linux-musl/8.3.0/crtfastmath.o
Full log can be found here: http://0x0.st/z2k6.txt
Also there was an issue raised in 2017: https://reviews.llvm.org/D28791
*(from redmine: issue id 10627, created on 2019-06-27)*3.10.6https://gitlab.alpinelinux.org/alpine/aports/-/issues/10116apache and mod_dav_svn segfaulting2021-11-17T13:54:26Zmatthew sporlederapache and mod_dav_svn segfaulting\#Dockerfile
FROM alpine:3.8
RUN apk add --no-cache apache2 mod_dav_svn subversion apache2-webdav apache2-utils curl
COPY subversion.conf /etc/apache2/conf.d/
COPY svnaccess.htpasswd svn_authz /etc/apache2/
RUN \
...\#Dockerfile
FROM alpine:3.8
RUN apk add --no-cache apache2 mod_dav_svn subversion apache2-webdav apache2-utils curl
COPY subversion.conf /etc/apache2/conf.d/
COPY svnaccess.htpasswd svn_authz /etc/apache2/
RUN \
sed -i 's@PidFile "/run/apache2/httpd.pid"@PidFile "/tmp/httpd.pid"@g' /etc/apache2/conf.d/mpm.conf && \
sed -i 's@#EnableMMAP off@EnableMMAP off@g' /etc/apache2/httpd.conf && \
sed -i 's@ErrorLog logs/error.log@ErrorLog /dev/stderr@g' /etc/apache2/httpd.conf && \
sed -i 's@Listen 80@Listen 6666@g' /etc/apache2/httpd.conf && \
sed -i 's@CustomLog logs/access.log combined@CustomLog /dev/stdout combined@g' /etc/apache2/httpd.conf;
\#subversion.conf
LoadModule dav_module modules/mod_dav.so
LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so
<VirtualHost *:6666>
ServerName _default_
<Directory /var/www/svn>
Require all granted
</Directory>
<Location /repos>
DAV svn
SVNParentPath /var/www/svn
AuthType Basic
AuthName "Authorization Realm"
AuthUserFile /etc/apache2/svnaccess.htpasswd
Require valid-user
AuthzSVNAccessFile /etc/apache2/svn_authz
</Location>
</VirtualHost>
\#\#\#\#the result
curl localhost:6666/repos/mysvn
\[Thu Mar 14 13:44:56.510692 2019\] \[core:notice\] \[pid 1\] AH00052:
child pid 8 exit signal Segmentation fault (11)
------------------------------------------------------------------------
This doesn’t happen on 3.7. ldd isn’t helpful with apache modules for
some reason (but probably unrelated since it is the same as 3.7)
3.9 is also impacted.
*(from redmine: issue id 10116, created on 2019-03-14)*3.8.5Kaarle RitvanenKaarle Ritvanenhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/9539Can't mount BTRFS volume using fstab2024-03-27T19:28:59ZLouis MatthijssenCan't mount BTRFS volume using fstabI installed Alpine on <code>/dev/sda</code> in <code>sys</code> mode
using <code>ext4</code>. Then I created a <code>btrfs</code> volume on
<code>/dev/sdb</code> and <code>/dev/sdc</code> using:
apk add btrfs-progs
modprobe btrf...I installed Alpine on <code>/dev/sda</code> in <code>sys</code> mode
using <code>ext4</code>. Then I created a <code>btrfs</code> volume on
<code>/dev/sdb</code> and <code>/dev/sdc</code> using:
apk add btrfs-progs
modprobe btrfs && echo btrfs > /etc/modules
mkfs.btrfs -m raid1 -d raid1 /dev/sdb /dev/sdc
mkdir /data && mount /dev/sdb /data
This is working fine. Now I add this mount to <code>/etc/fstab</code>
like this:
UUID=da110dca-aed5-48b8-a5b6-c1b41c10c419 /data btrfs defaults 0 0
On reboot I get the following error:
mount: mounting /dev/sdc on /data failed: Invalid argument
Output of <code>dmesg</code>:
[ 5.950849] BTRFS: device fsid da110dca-aed5-48b8-a5b6-c1b41c10c419 devid 2 transid 12 /dev/sdc
[ 5.952786] BTRFS info (device sdc): disk space caching is enabled
[ 5.952791] BTRFS info (device sdc): has skinny extents
[ 5.954055] BTRFS warning (device sdc): devid 1 uuid 6a45e7d4-78df-4263-be09-b83a3a15e6e0 is missing
[ 5.954063] BTRFS error (device sdc): failed to read the system array: -5
[ 6.002364] BTRFS error (device sdc): open_ctree failed
I fixed this by adding <code>/sbin/btrfs device scan</code> to the top
of the <code>start</code> method in <code>/etc/init.d/localmount</code>.
However, I have a feeling that this command is already ran on boot but
only *after* mounting <code>/etc/fstab</code>, because when I simply run
<code>mount /dev/sdb /data</code> right after booting it’s working.
It seems that this command is being called if the root file system is
<code>btrfs</code> (see \#6903); I think this should also be done if
there is any other <code>btrfs</code> file system in
<code>/etc/fstab</code>.
*(from redmine: issue id 9539, created on 2018-10-08)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/7780Volume containing apkovl is not remounted according to the apkovl's /etc/fsta...2023-04-30T01:34:09ZalgitbotVolume containing apkovl is not remounted according to the apkovl's /etc/fstab entryTo reproduce:
1) make a new VM, attach the alpine-virtual iso and a blank virtual disk
as /dev/sda
2) run setup-alpine, selecting a data-only install, mounting to /var
3) set LBU\_BACKUPDIR=/var and run lbu commit
4) reboot and o...To reproduce:
1) make a new VM, attach the alpine-virtual iso and a blank virtual disk
as /dev/sda
2) run setup-alpine, selecting a data-only install, mounting to /var
3) set LBU\_BACKUPDIR=/var and run lbu commit
4) reboot and observer that /dev/sda2 is mounted to /media/sda2, not
/var
Cause: The initramfs /init script is supposed to unmount the device that
the apkovl was found on, after it has been unpacked. There is still
logic to unmount a device stored in $ovl\_unmount, but commit
ba27888b4576ceab7413ab9104d0aeda50990832 (which moved the apkovl search
logic out to nlplug-findfs) removed the last line that set that
variable, and as far as I can tell even the old code never unmounted
non-usb devices correctly.
Fix: Set $ovl\_unmount to the apkovl device unless it is used as the
sysroot? (This might cause a conflict if the apkovl is stored on a
boot\_repository device; IDK.)
*(from redmine: issue id 7780, created on 2017-09-01)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/15892busybox: not possible to permanently remove klogd user2024-03-19T21:47:08ZNatanael Copabusybox: not possible to permanently remove klogd userCommit b870258c717220a2ea3f8803e54578ee80820979 (main/busybox: run klogd as klogd user and not root) introduced a user named `klogd` that is created from busybox install script. A consequence of this is that users who don't want this use...Commit b870258c717220a2ea3f8803e54578ee80820979 (main/busybox: run klogd as klogd user and not root) introduced a user named `klogd` that is created from busybox install script. A consequence of this is that users who don't want this user on their system can not remove it without it gets recreated on next busybox upgrade. And since it is not really possible to uninstall busybox, it means that it is not really possible to permanently remove the `klogd` user.
Possible solutions:
1. Move the `klogd` user to default `/etc/passwd` provided by `alpine-baselayout`. Users can simply `deluser klogd`, and it will not automatically come back on upgrades. This is the solution I prefer. It is very simple, and the drawback is insignificant (`klogd` user is there by default even if you never install `busybox-openrc`).
2. Move the user creation to `busybox-openrc.pre-install`. Users can avoid creating the `klogd` user with `apk add !busybox-openrc` and not use any of the busybox provided services. There should be alternatives to those, but in this case you cannot use any of the busybox provided services.
3. Split `busybox-openrc`, and ship every service in a separate package. The `klogd` user would be created with `busybox-klogd-openrc` package. I really don't want to do this, because it adds a lot complexity with high risk of unexpected breakages and it has very low benefit.
4. let the install script parse some config where you can disable creation. For example, source `/etc/conf.d/klogd` and see if `command_user=klogd`https://gitlab.alpinelinux.org/alpine/aports/-/issues/13255[3.15] postgresql dependency fight2021-11-30T12:06:22ZDavid Heidelberg[3.15] postgresql dependency fightEmpty environment:
```
$ apk update
...
```
```
# apk add postgresql-libs
WARNING: Ignoring /mnt/pmbootstrap-packages: No such file or directory
(1/2) Installing libpq (14.1-r3)
(2/2) Installing postgresql-bdr-libs (9.4.14_p1-r12)
```
``...Empty environment:
```
$ apk update
...
```
```
# apk add postgresql-libs
WARNING: Ignoring /mnt/pmbootstrap-packages: No such file or directory
(1/2) Installing libpq (14.1-r3)
(2/2) Installing postgresql-bdr-libs (9.4.14_p1-r12)
```
```
# apk add gcc musl-dev postgresql-dev
WARNING: Ignoring /mnt/pmbootstrap-packages: No such file or directory
ERROR: unable to select packages:
libecpg-14.1-r3:
conflicts: postgresql-bdr-libs-9.4.14_p1-r12[so:libecpg.so.6=6.14]
postgresql-bdr-libs-9.4.14_p1-r12[so:libpgtypes.so.3=3.14]
satisfies: libecpg-dev-14.1-r3[libecpg=14.1-r3]
postgresql-bdr-libs-9.4.14_p1-r12:
conflicts: libecpg-14.1-r3[so:libecpg.so.6=6.6]
libecpg-14.1-r3[so:libpgtypes.so.3=3.5]
satisfies: world[postgresql-libs]
```
Verified on 2 environments [amd64, aarch64]. Regression, since the 3.14 image works as expected.https://gitlab.alpinelinux.org/alpine/aports/-/issues/13224Install php8-pecl-imagick 3.5.0-r0 failing2022-03-22T11:17:12ZP PandaInstall php8-pecl-imagick 3.5.0-r0 failingWhen adding php8-pecl-imagick 3.5.0-r0 on alpine-3.14 failing with following
```
fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/main/aarch64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/community/aarch64/APKINDEX....When adding php8-pecl-imagick 3.5.0-r0 on alpine-3.14 failing with following
```
fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/main/aarch64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/community/aarch64/APKINDEX.tar.gz
ERROR: unable to select packages:
so:libMagickCore-7.Q16HDRI.so.9 (no such package):
required by: php8-pecl-imagick-3.5.0-r0[so:libMagickCore-7.Q16HDRI.so.9]
so:libMagickWand-7.Q16HDRI.so.9 (no such package):
required by: php8-pecl-imagick-3.5.0-r0[so:libMagickWand-7.Q16HDRI.so.9]
```
Probably happening since imagemagick 7.0.11.14-r0J0WIJ0WIhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12353setup-disk with sys mode on Raspberry Pi 3.13.02022-06-20T23:50:47ZWilli Hubersetup-disk with sys mode on Raspberry Pi 3.13.0Commit "setup-disk: add rpi support" does not work on RPI.
Run command:
**setup-disk -m sys /mnt**
Always get error
Ext4 is not supported. Only supported are: VFAT"
Problem in source code :
```sh
supported_boot_fs() {
local supp...Commit "setup-disk: add rpi support" does not work on RPI.
Run command:
**setup-disk -m sys /mnt**
Always get error
Ext4 is not supported. Only supported are: VFAT"
Problem in source code :
```sh
supported_boot_fs() {
local supported="ext2 ext3 ext4 btrfs xfs vfat"
local fs=
**if is_rpi; then
supported=vfat
fi**
for fs in $supported; do
[ "$fs" = "$1" ] && return 0
done
```
Fresh install with Alpine Linux 3.12.3 no problem3.14.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/12309net-snmp not working on Alpine 3.13 (amd64)2022-11-19T07:09:09ZStefano Marinellinet-snmp not working on Alpine 3.13 (amd64)Both on updated Alpine 3.12->3.13 hosts and newly created Alpine 3.13 hosts, snmpd kills itself just after being launched. dmesg reports:
`traps: snmpd[21440] general protection fault ip:7f7bbd9efc59 sp:7ffd4e6df8e0 error:0 in ld-musl-...Both on updated Alpine 3.12->3.13 hosts and newly created Alpine 3.13 hosts, snmpd kills itself just after being launched. dmesg reports:
`traps: snmpd[21440] general protection fault ip:7f7bbd9efc59 sp:7ffd4e6df8e0 error:0 in ld-musl-x86_64.so.1[7f7bbd9e1000+48000]`
Removing the trapsink on snmpd.conf, it seems to be running but dmesg reports:
`snmpd[22073]: segfault at 7f7598021110 ip 00007f759859d215 sp 00007ffed55515e0 error 6 in libnetsnmpmibs.so.40.0.0[7f759858b000+ab000]
Code: 09 f0 f3 48 0f 2a c8 f3 0f 58 c9 f3 0f 5e c1 f3 0f 58 05 22 b1 09 00 f3 0f 2c c0 c3 53 e8 53 0e ff ff 48 89 c7 48 85 c0 74 1a <48> 83 a7 70 20 00 00 df 48 c7 87 68 20 00 00 ff ff ff ff e8 c3 33`
Still, there seem to be some stability problems as after some pollings it seems to kill itself.Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12057tzdata corrupted files in lasted releases of alpine2021-01-05T13:26:22ZPICCORO Lenz McKAYtzdata corrupted files in lasted releases of alpineas dicuss in https://lists.alpinelinux.org/~alpine/users/%3CCAEpSaE0Qj32d-6e6mk3AG6dXouSv2MAtPR8bGJra0i15oaLj2A%40mail.gmail.com%3E#%3Cem69ec0234-0de9-4a25-a044-95cac558748b@elzian%3E tzdata has some problems ..
on docker alpine, since...as dicuss in https://lists.alpinelinux.org/~alpine/users/%3CCAEpSaE0Qj32d-6e6mk3AG6dXouSv2MAtPR8bGJra0i15oaLj2A%40mail.gmail.com%3E#%3Cem69ec0234-0de9-4a25-a044-95cac558748b@elzian%3E tzdata has some problems ..
on docker alpine, since 3.10 to 3.12:
```
FROM alpine:3.11.0
ENV TZ=Asia/Jerusalem
RUN apk add -U tzdata
RUN cp /usr/share/zoneinfo/Asia/Jerusalem /etc/localtime
RUN apk update
RUN apk upgrade
RUN apk add ca-certificates && update-ca-certificates
gets the date in IST timezone (2 hours from utc), example :
Tue Oct 27 *09*:06:24 *IST* 2020
Same image created now is on UTC timezone, but does not even state "UTC"
,example (run at the very same time):
Tue Oct 27 *07*:06:24 2020
```
resolved this by copying
/usr/share/zoneinfo/Asia/Jerusalem
From old image to the new container (file size is also double), but this of
course is not a good solutionhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11670targetcli does not succesfully restore config2020-11-09T13:35:25ZAlain van Hooftargetcli does not succesfully restore configAfter configuring targetcli and saving config, config is not restored after a reboot, or when loaded via commandline. Both due to this error:
targetcli restoreconfig
restore_from_file() takes from 1 to 4 positional arguments but 5 were ...After configuring targetcli and saving config, config is not restored after a reboot, or when loaded via commandline. Both due to this error:
targetcli restoreconfig
restore_from_file() takes from 1 to 4 positional arguments but 5 were given
Note: "targetctl restore" does work.https://gitlab.alpinelinux.org/alpine/aports/-/issues/10478Package 'nginx-mod-http-lua' breaks nginx2021-06-13T01:14:21ZZach van RijnPackage 'nginx-mod-http-lua' breaks nginxRecent versions of <code>nginx-mod-http-lua</code> have broken nginx
with the default configuration. There has been [much
activity](https://git.alpinelinux.org/aports/log/main/nginx) on this
package lately, and therefore it is not easy t...Recent versions of <code>nginx-mod-http-lua</code> have broken nginx
with the default configuration. There has been [much
activity](https://git.alpinelinux.org/aports/log/main/nginx) on this
package lately, and therefore it is not easy to pinpoint the breaking
change.
A [related
discussion](https://github.com/openresty/lua-nginx-module/issues/1509)
has determined that one must add <code>lua\_load\_resty\_core
off;</code> to the nginx configuration.
I have tested this issue on Alpine 3.8 and 3.9 as of 2019-05-19.
**To Reproduce:**
1. Launch a fresh copy of Alpine, update and upgrade.
2. <code>\# apk add nginx-mod-http-lua</code>
3. <code>\# nginx</code>
You will be greeted with something like:
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:
no field package.preload['resty.core']
no file './resty/core.lua'
no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua'
no file '/usr/local/share/lua/5.1/resty/core.lua'
no file '/usr/local/share/lua/5.1/resty/core/init.lua'
no file '/usr/share/lua/5.1/resty/core.lua'
no file '/usr/share/lua/5.1/resty/core/init.lua'
no file '/usr/share/lua/common/resty/core.lua'
no file '/usr/share/lua/common/resty/core/init.lua'
no file './resty/core.so'
no file '/usr/local/lib/lua/5.1/resty/core.so'
no file '/usr/lib/lua/5.1/resty/core.so'
no file '/usr/local/lib/lua/5.1/loadall.so'
no file './resty.so'
no file '/usr/local/lib/lua/5.1/resty.so'
no file '/usr/lib/lua/5.1/resty.so'
no file '/usr/local/lib/lua/5.1/loadall.so')
nginx: [emerg] open() "/run/nginx/nginx.pid" failed (2: No such file or directory)
One might think we need to install OpenResty:
<code>\# apk add $(apk search **resty** | awk <s>F’\[</s>\]’ ‘{print $1
“-” $2 “-” $3}’)</code>
This does not resolve the issue. It appears that we need
<code>lua-resty-core</code>, but this is not packaged on Alpine at this
time.
**Possible Workaround:**
If we instead add <code>lua\_load\_resty\_core off;</code> to the nginx
<code>http { }</code> configuration, we still get the OpenResty warning
above, but not the missing libraries, and nginx starts as expected.
A better solution would be to fix the package. This type of issue
catches system administrators by surprise and can be incredibly
frustrating.
ZV
*(from redmine: issue id 10478, created on 2019-05-21)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/8894Qemu-Guest-Agent not working2023-08-05T19:18:15ZFelix Drescher-HackelQemu-Guest-Agent not workingHey folks,
im currently using Alpine Linux 3.7 on Proxmox VE 5.1.
I enabled all repositories and installed the package
“qemu-guest-agent”.
I also set the “Qemu Agent” option inside Proxmox and by checking the
Process lists, i can con...Hey folks,
im currently using Alpine Linux 3.7 on Proxmox VE 5.1.
I enabled all repositories and installed the package
“qemu-guest-agent”.
I also set the “Qemu Agent” option inside Proxmox and by checking the
Process lists, i can confirm that Proxmox actually attaches the guest
agent socket.
For some reason, the qemu-guest-agent service instantly crashes.
Executing the command “qemu-ga” manually, leads to this output:
![](http://i.epvpimg.com/b7nxgab.png)
Can you give me any advice how to fix this?
Yes… i already restarted the machine. Several times.
Ive talked to the Proxmox Guys and now it seems clear that this bug is
more related to Alpine itself.
So, i hope you know what’s causing this behavior.
*(from redmine: issue id 8894, created on 2018-05-16)*3.8.5https://gitlab.alpinelinux.org/alpine/aports/-/issues/8762Maven Package making MAVEN_OPTS difficult to set2022-06-20T04:57:46ZalgitbotMaven Package making MAVEN_OPTS difficult to setSetting -Xmx in ENV MAVEN\_OPTS on the dockerfile doesn’t seem to work
because the /etc/mavenrc is setting it and putting the Xmx to the end of
the arguments.
Wouldn’t be better to let the JVM set the default Heap Size or let the
user ...Setting -Xmx in ENV MAVEN\_OPTS on the dockerfile doesn’t seem to work
because the /etc/mavenrc is setting it and putting the Xmx to the end of
the arguments.
Wouldn’t be better to let the JVM set the default Heap Size or let the
user set MAVEN\_OPTS easily in the Dockerfile with ENV?
*(from redmine: issue id 8762, created on 2018-04-03)*