-
Notifications
You must be signed in to change notification settings - Fork 11.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
Docker Image CI Workflow failing #2384
Comments
Update: just asked on that bug and they pointed me to the cause. |
Hmm. Thanks for pointing out the issue. I think we should fix versions as suggested here to avoid such problem. This would require us to commit This way we would manually update our And to fix this one, I think we may need to downgrade our Gemfile to not use the latest version of this library.
What do you think about all this? |
I agree, we should commit |
Specify an older version of |
Can you test this combination?
|
I am getting the same issue when I am running docker compose up command, what should I do to rectify it? |
Hi @george-gca, Also, we may have to provide two Other than that, current users shouldn't have any problems. For your case, you shouldn't use |
Why 2
|
Is this conversation related to this build error: "Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: kitabisa/[email protected]" |
It is not related, but I will open a PR for this. Thanks for noticing. |
Hi @george-gca, This is my Gemfile.lock as you have requested. Changing versions should be done via this lock file. Feel free to change it and fix it if you can. But the problem is not solved. Also, I say maybe we should have two versions since each library has different versions for different cpu architectures.
|
@pourmand1376 I run my jekyll site locally without Docker and it is working. Here is my
|
Btw, using both my
|
This PR should fix the issues reported in alshedivat/al-folio#2384 , alshedivat/al-folio#2392 and alshedivat/al-folio#2395. It seems that the ruby docker image is not affected by these problems.
This PR should fix the issues reported in alshedivat#2384 , alshedivat#2392 and alshedivat#2395. It seems that the ruby docker image is not affected by these problems.
This PR should fix the issues reported in alshedivat/al-folio#2384 , alshedivat/al-folio#2392 and alshedivat/al-folio#2395. It seems that the ruby docker image is not affected by these problems.
This PR should fix the issues reported in alshedivat#2384 , alshedivat#2392 and alshedivat#2395. It seems that the ruby docker image is not affected by these problems.
This PR should fix the issues reported in alshedivat/al-folio#2384 , alshedivat/al-folio#2392 and alshedivat/al-folio#2395. It seems that the ruby docker image is not affected by these problems.
@george-gca |
Maybe you need to update your repo. Probably some changes were made to the docker image that are affecting your local repo. |
For anyone who does not want to rebase their branch for whatever reason, updating Dockerfile and Gemfile to v0.12.0 fixed this for me. |
This PR should fix the issues reported in alshedivat#2384 , alshedivat#2392 and alshedivat#2395. It seems that the ruby docker image is not affected by these problems.
This PR should fix the issues reported in alshedivat#2384 , alshedivat#2392 and alshedivat#2395. It seems that the ruby docker image is not affected by these problems.
Have you checked that your issue isn't already filed?
Bug description
Docker Image CI Workflow is failing due to
mini_racer
How to reproduce the bug
Check the failed action.
Error messages and logs
Error message of interest:
What operating system are you using?
Not applicable (e.g. you're using GitHub Pages or other hosting)
Where are you seeing the problem on?
Deployed site
More info
It is probably due to
mini_racer
version0.12.0
. I checked their repo and found this issue. Can you take a look at it @pourmand1376?The text was updated successfully, but these errors were encountered: