Skip to content

Krakend Official Docker Image Libc Inconsistency #1082

@dschanoeh

Description

@dschanoeh

Environment info:

  • KrakenD version: 2.13.4
  • System info: Official krakend docker image 2.13.4

Commands used:

krakend check-plugin -l "$GLIBC" -s "$PLUGIN"

Logs:
libc
have: MUSL-1.2.5_(alpine-3.23.4)
want: MUSL-1.2.5_(alpine-3.23.3)

Additional comments:
I'm executing above command in the official krakend image to check whether my plugins would be compatible with it.
I believe the error message I'm getting indicates that there is a libc difference between the krakend binary in the image and the alpine base image. The corresponding krakend/builder also uses 3.23.3 and not 3.23.4.

This should be consistent, right? Or is it expected that this can happen and I need to work around it?
Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions