You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent container images are showing failures with dependencies when running schema or help output:
docker run --rm -it ghcr.io/fluent/fluent-bit/unstable:master --help
...
/fluent-bit/bin/fluent-bit: error while loading shared libraries: libldap_r-2.4.so.2: cannot open shared object file: No such file or directory
The following versions are fine:
fluent/fluent-bit:2.1.2
fluent/fluent-bit:2.0.11
ghcr.io/fluent/fluent-bit/unstable:2.0
It therefore seems to be an issue with a recent merge to master as the 2.0 branch is ok.
To Reproduce
Run a container built from master, e.g.
$ docker run --pull=always --rm -t ghcr.io/fluent/fluent-bit/master:x86_64 --help
Unable to find image 'ghcr.io/fluent/fluent-bit/master:x86_64' locally
x86_64: Pulling from fluent/fluent-bit/master
...
Digest: sha256:fe576aa51c55acc70b3cd2b4de5ad2f202ff6e8e3ecab2a475da6ca470e42275
Status: Downloaded newer image for ghcr.io/fluent/fluent-bit/master:x86_64
/fluent-bit/bin/fluent-bit: error while loading shared libraries: libldap_r-2.4.so.2: cannot open shared object file: No such file or directory
Steps to reproduce the problem:
Expected behavior
No dependency failure.
Screenshots
Your Environment
Version used:
Configuration:
Environment name and version (e.g. Kubernetes? What version?):
Server type and version:
Operating System and version: Ubuntu 22.04
Filters and plugins:
Additional context
The text was updated successfully, but these errors were encountered:
I think this is triggered by #7309 - we updated the production container to use the latest LDAP (2.5.0) but not the builder container so it is depending on the old version of 2.4.
Bug Report
Describe the bug
Recent container images are showing failures with dependencies when running schema or help output:
The following versions are fine:
It therefore seems to be an issue with a recent merge to
master
as the2.0
branch is ok.To Reproduce
Run a container built from master, e.g.
Expected behavior
No dependency failure.
Screenshots
Your Environment
Additional context
The text was updated successfully, but these errors were encountered: