-
-
Notifications
You must be signed in to change notification settings - Fork 223
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
Building the containers locally throws an error #20
Comments
It might not be relevant be is there any reason the containers need to be built with |
Could you please share your host system? I you are using a Linux system, the following command should give enough information: $ cat /etc/*release* In the past, I had some issues to build a statically linked binary of
We are using |
Of course no problem. Here is my host system information: $ cat /etc/*release*
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="0;36"
HOME_URL="https://www.archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
LOGO=archlinux
From what I read in the comments, it looks like you are not far away from the solution. I am not familiar with Haskell but I will see if I can help you in that (my job makes me really busy lately ^^').
I can run it on my own machine without So I think it might be true in the past but I don't think it's needed anymore nowadays. It looks like most distributions rather encourage you to add yourself in the |
I don't really know why but it's running fine on an Ubuntu host. It looks like another issue with Docker on an Arch Linux host.
I'm not familiar with Haskell either but thankfully the Haskell community provides some good help 😉
You are absolutely right. I might add a note on the README to state that I've created a branch where I'm using an Ubuntu base image with
Thanks for your help 👍 |
I think this problem reported in this issue comes from the fact that the mermaid container uses puppeteer. As puppeteer uses Chrome under the hood, it needs specific configuration to make it run indide a container (or do privilege escalation and run the container with So I guess But I don't think the problem is the same as the one in the I'll try to test your branch and give you a feedback this weekend. 👍 |
It was somehow related to Puppeteer because upgrading Puppeteer to the latest version fixed this issue.
Indeed, in this case the error happens during
Awesome, thanks! |
It looks like the build for this container worked on the Sorry for the delay. 😅 |
Thanks for your input! |
The current behaviour
When we try to build the project's container, I get the following error
cabal: Failed to build graphviz-2999.6.0.0. See the build log above for details.
.Ouput of
sudo make buildDockerImages
:Expected behaviour
The containers images should be built without any issue
Way to reproduce the error
git clone
the repositorysudo make buildDockerImages
Thanks in advance for your help.
The text was updated successfully, but these errors were encountered: