Get help with testing, discuss unit testing strategies etc.


Post by paulb »

Hi,
we are trying to use Siesta in an Alpine Docker Container. We use webdriver and chrome for our tests. Out-of-the-box it does not work and exits with a status code of 127. Upon further inspection it seems that the chromedriver and node executables bundled with Siesta simply do not work in Alpine and we have to use the correct Alpine versions of it. We do this by linking the installed version into the respective directories.
Is there any way to do this more "cleanly"? Like a config option that can set a path to the correct chromedriver and node versions or using the versions in the PATH?


Post by nickolay »

Hello,

it seems that the chromedriver and node executables bundled with Siesta simply do not work in Alpine

Any additional details? Perhaps you mean that version of Chrome in Alpine container is too new for chromedriver binary, bundled with Siesta? In such case you need to update the Siesta's chromedriver manually (/bin/binary/chromedriver)


Post by paulb »

The problem is that Alpine uses lib-musl instead of lib-c. This means that binaries from other distributions do not work.


Post by nickolay »

I see. So you use a custom binary of chromedriver that expects lib-musl? Then you just place it into /bin/binary/chromedriver/os


Post by paulb »

Thats what we are already doing, replacing the packaged versions inside /bin/binary/chromedriver/linux64.
So I guess there is no other way to do it then?


Post by nickolay »

Nope


Post by paulb »

Ok, thanks for your support and quick anwsers!


Post by nickolay »

Sure, yw


Post Reply