-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
fix(docker): run in docker, and build scripts for docker #1291
Conversation
…is runs headless, no errors from chromium or puppetteer
Love this! Does docker-compose come with installs on Windows? I know for macOS and Linux you need to install separately, so it would need to be a prerequisite. |
Docker Compose does come installed in the docker desktop app on windows |
On second thought, I'm a little hesitant on the I'd also like to add that it's somewhat verbose given we can use That being said, I really like the changes and it seems to be working great on my end. I appreciate your contribution and would like to hear your thoughts! Thanks. |
…stening, setting it as disabled default in docker-compose, and adding docs for how to build docker
🤷♀️ I could change the Obviously I like docker-compose and Makefiles, because it makes it super easy to get started without even reading any docs 😁 I see makefiles and docker-compose as build tools, once you get them going, they kinda work without much attention (caveat: if you have complex systems, your build tools will get complex, this is not complex). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, I see where you're coming from. If you don't mind though, I'll make a couple suggestions and you let me know what you think.
I really appreciate your contribution and your time for the input and feedback!
@@ -0,0 +1,14 @@ | |||
version: '3.0' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
version: '3.0' | |
version: '3.8' |
Let's pin to the latest version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't tested if this docker-compose is compatible with v3.8 compose file.
these versions are for the docker-compose.yml
file, across the versions some add more features at the cost of mandatory complexity.
We can stick with v3.0 of docker-compose file until the end of days (caveat: if we do not need any functionality from greater versions, and do not mind slight change of syntax).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay! I can get with that. Since we're pinning to 3.0
, that makes sense to me.
Co-authored-by: Jef LeCompte <jeffreylec@gmail.com>
Co-authored-by: Jef LeCompte <jeffreylec@gmail.com>
Co-authored-by: Jef LeCompte <jeffreylec@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing work!!! I really appreciate your feedback and the time you took to implement this.
Updates unnecessary need to grant special privileges when running in Docker.
the Docker image was unfortunately only built for amd64 and therefore does not work on my Helios64 with rockchip64 (arm64/v8) architecture. here the output from Helios64...
edit: My customized Dockerfile with "node:14.15.3-buster" instead of "node:14.15.0-alpine3.12".
however there seems to be a problem installing chromium or?
edit3:
and here the log of the running container...
|
I am able to run fine without the SYS_ADMIN parameter (less of a security risk). I have included some build instructions in my fork which i am keeping up to date with the main branch with some minor tweaks for unraid usage: |
It has already been merged /close |
i first had the problem on my helios with aarch64 and was able to work around it. aarch64... armv7l... should I rather create a new issue for this or can we discuss it further here? |
If you're having problems with install the Chromium browser, it's because of the package manager used in alpine is I prefer that we keep this image using alpine, as it should work on most systems. If you'd like make this work for your ARM architecture, I think you should change the image to use |
@jef the problem no longer exists for the Helios64 arm64v8, there it worked in the end, because for this there is the Chromium package at alpine. I am currently testing to rewrite the Dockerfile so that I work with buster-slim, since there should be the Chromium package on all architectures. |
no reason to grant excessive permissions to your docker container, this runs headless, no errors from chromium or puppetteer.
Description
This also prints the config for puppetteer, makes it easier to troubleshoot:
no more this error when running in docker
Testing
Running
make
will do everything for youNew dependencies