File in /opt folder in APK ends up in /bin folder in final image

[pettermk]

Hi,

I am running a pipeline where we are building some custom images nightly (melange + apko). The pipeline started failing 5 days ago, where an executable in /opt/ now ends up in the /bin/ folder (other than that, things work). I've verified the package which is built by melange, that the file is in the correct location, so it looks like something changed in the way the package is handled in apko

This spawns the question what would be the recommended location for a statically built go binary, perhaps my scripts are wrong? In any case I thought I would report this change of behavior in case it was not intended.

Thanks for wolfi, melange and apko!

[kaniini]

Could you provide the output of tar ztvf $yourAPK?

[pettermk]

Sure:

[petter@fedora container-base-images-main]$ tar ztvf melange/packages/x86_64/oauth2-proxy-7.4.0-r0.apk
-rw-r--r-- root/root       512 1970-01-01 01:00 .SIGN.RSA.melange.rsa.pub
-rw-r--r-- root/root       267 1970-01-01 01:00 .PKGINFO
drwxr-xr-x root/root         0 1970-01-01 01:00 opt
tar: Ignoring unknown extended header keyword 'APK-TOOLS.checksum.SHA1'
-rwxr-xr-x root/root  25529465 1970-01-01 01:00 opt/oauth2-proxy
drwxr-xr-x root/root         0 1970-01-01 01:00 var
drwxr-xr-x root/root         0 1970-01-01 01:00 var/lib
drwxr-xr-x root/root         0 1970-01-01 01:00 var/lib/db
drwxr-xr-x root/root         0 1970-01-01 01:00 var/lib/db/sbom
tar: Ignoring unknown extended header keyword 'APK-TOOLS.checksum.SHA1'
-rw-r--r-- root/root      2113 1970-01-01 01:00 var/lib/db/sbom/oauth2-proxy-7.4.0-r0.spdx.json