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
When building a docker container with markojs and marko-cli dependencies on an armhf target, the container build fails due to the chromedriver dependency of @marko/test, that is a dependency of marko-cli.
chromedriver is not available on armhf targets (I guess it's not available for any arm target).
Possible Workaround
I managed to build a docker image setting ENV CHROMEDRIVER_SKIP_DOWNLOAD=true in the Dockerfile.
We don't run tests on our markojs files while building the containers, so it's a "safe" workaround for us.
Additional Info
Your Environment
Ubuntu image on arm8l
Kernel 4.15.0
docker 18.09.5
Steps to Reproduce
You need an armhf-capable docker builder to reproduce this.
The text was updated successfully, but these errors were encountered:
When building an armhf docker container, marko-cli now fails when installing pngquant-bin, dependency brought in by imagemin-webpack-plugin from @marko/build.
Reported error is:
pngquant failed to build, make sure that libpng-dev is installed
although libpng-dev is installed in the building docker image (along with all the necessary make/gcc/g++... build dependencies).
There is no workaround for this, not sure if switching to imagemin-webpack and making the image plugins optional could be an option to solve this issue.
I'm partial to making image optimization steps not run on every build, as long as every build checks to make sure images don’t exceed some threshold of bytes:pixel ratio. That would also let us move imagemin-webpack into optionalDependencies.
[email protected]
Details
When building a docker container with
markojs
andmarko-cli
dependencies on anarmhf
target, the container build fails due to thechromedriver
dependency of@marko/test
, that is a dependency ofmarko-cli
.chromedriver
is not available onarmhf
targets (I guess it's not available for any arm target).Possible Workaround
I managed to build a docker image setting
ENV CHROMEDRIVER_SKIP_DOWNLOAD=true
in theDockerfile
.We don't run tests on our markojs files while building the containers, so it's a "safe" workaround for us.
Additional Info
Your Environment
arm8l
Steps to Reproduce
You need an
armhf
-capable docker builder to reproduce this.The text was updated successfully, but these errors were encountered: