Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot install on armhf targets #133

Open
MiloCasagrande opened this issue Jun 21, 2019 · 2 comments
Open

Cannot install on armhf targets #133

MiloCasagrande opened this issue Jun 21, 2019 · 2 comments

Comments

@MiloCasagrande
Copy link
Contributor

[email protected]

Details

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.

@MiloCasagrande
Copy link
Contributor Author

Update for [email protected]

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.

@tigt
Copy link
Contributor

tigt commented Jul 20, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants