Open kgmishra786 opened 2 years ago
Which version of StackStorm and Helm chart you're using? Does it match ? https://github.com/StackStorm/st2packs-dockerfiles/blob/a536a212766cf69c69f74d348c5ecdc5deaa3485/st2packs-builder/Dockerfile#L1
Hi,
Good Day!
We are also experiencing similar issue. Error - /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found
We are building docker image like this - ARG PACKS="file:///st2packs/test file:///st2packs/test2" FROM stackstorm/st2packs:builder AS builder COPY test /st2packs/test/ RUN ls -la /st2packs/test/ COPY test2 /st2packs/test2/ RUN ls -la /st2packs/test2/ RUN /opt/stackstorm/st2/bin/st2-pack-install ${PACKS} FROM stackstorm/st2packs:runtime
It was all working fine before, now we are getting above error. Has anyone found solution for this issue?
Need help for the same.
Thanks
https://github.com/StackStorm/st2packs-dockerfiles/blob/a536a212766cf69c69f74d348c5ecdc5deaa3485/st2packs-builder/Dockerfile#L1 @subhashkakkar Same questions, which version of the st2 you're using, which st2 version was before, which version of st2 stackstorm/st2packs-builder relies on? The versions should match.
Hi @armab -
I am using 3.5dev version of st2. It was the same before as well. Nothing has been changed.
stackstorm/st2packs-builder is taking latest from library (which i believe is same from last 4 years) - https://hub.docker.com/r/stackstorm/st2packs-builder
stackstorm/st2pack is taking latest from library, this has been updated 2 months back - https://hub.docker.com/r/stackstorm/st2packs/dockerfile.
My current Docker file code - ARG PACKS="file:///st2packs/test file:///st2packs/test2" FROM stackstorm/st2:3.5dev FROM stackstorm/st2packs:builder AS builder COPY test /st2packs/test/ RUN ls -la /st2packs/test/ COPY test2/st2packs/test2/ RUN ls -la /st2packs/test2/ RUN /opt/stackstorm/st2/bin/st2-pack-install ${PACKS} FROM stackstorm/st2packs:runtime
Thanks & Regards, Subhash Kakkar
@subhashkakkar The https://github.com/StackStorm/st2packs-dockerfiles/blob/a536a212766cf69c69f74d348c5ecdc5deaa3485/st2packs-builder/Dockerfile#L1 relies on v3.7.
You need to rely on the same st2 version to build the packs.
Something like this would work better:
ARG PACKS="file:///tmp/stackstorm-st2"
FROM stackstorm/st2:3.5 AS builder
# considering you have your "local" pack under the `stackstorm-st2` dir relative to Dockerfile
# Here we copy local "stackstorm-st2" dir into Docker's "/tmp/stackstorm-st2"
COPY ./st2packs/<PACK_DIR> /tmp/stackstorm-st2/
# Check it
RUN ls -la /tmp/stackstorm-st2
RUN /opt/stackstorm/st2/bin/st2-pack-install ${PACKS}
FROM stackstorm/st2packs:runtime
compared to the example in https://github.com/StackStorm/st2packs-dockerfiles#building-the-st2packs-image
We are deploying custom packs in AKS using Helm and custom pack image is build using below docker file: dockerfile:
FROM stackstorm/st2packs:builder AS builder COPY stackstorm-st2 /tmp/stackstorm-st2/ RUN ls -la /tmp/stackstorm-st2 RUN /opt/stackstorm/st2/bin/st2-pack-install file:///tmp/stackstorm-st2/custom_pack FROM stackstorm/st2packs:runtime
We are running pipeline to build docker image and then running BlackDuck scan and finally deploying in AKS. Till 20 Sep 2022 is was working as expected and from 22 Sep 2022 onwards we started getting below error when running packs: { "stdout": "", "stderr": "/opt/stackstorm/virtualenvs/custome_pack/bin/python: /lib/x86_64-linux-gnu/libm.so.6: version 'GLIBC_2.29' Not found" (required by /opt/stackstorm/virtualenvs/custome_pack/bin/python)\n/opt/stackstorm/virtualenvs/custome_pack/bin/python: /lib/x86_64-linux-gnu/libc.so.6: version 'GLIBC_2.28' Not found (required by /opt/stackstorm/virtualenvs/custome_pack/bin/python)\n, "exit_code":1, ""result": "None" }
In order to analyze it we deployed the same custom pack(Image build with same packs) build before 21st September its not giving any error however when we rebuild the same code and create new image, post deployment of the newly created image packs start giving error as mentioned above.
One more thing even our BlackDuck scan started failing for the newly created Images.
as we using below image in order to create custom Image, We suspect some issue with this image: stackstorm/st2packs:builder stackstorm/st2packs:runtime
Could someone please help me for this.