-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Could not connect to the PostCSS server (RuntimeError) #29
Comments
You need node js to use post css. I assume that the Jekyll image does not include it. |
@mhanberg thanks for your input.. I did following: |
@olakara Please remove the env var JEKYLL_ROOTLESS and try again. |
I am seeing this same error when I attempt to deploy via Netlify. I feel like I'm doing something silly with my config. Netlify Support Post: Github Branch with all of my attempts: |
@rwgrier there is a 404 on your link |
@Atem18 Sorry, I got kinda frustrated and gave up on it. I moved to a generated version of the Tailwind CSS file. |
@rwgrier No problem, if you ever want to see a working example, please see my website here : https://github.com/Atem18/atemlire |
@Atem18 I cloned your repo https://github.com/Atem18/atemlire.git and tried to run .. and ended up with the same error: all I did was run this command: |
@olakara If you go upper, you will see the real error. It's probably because the node_modules are missing. I pushed an update to my repo and the trick is to build your own image and override the ENTRYPOINT because for whatever reason, there is nodejs in the official Jekyll docker image but while it does install the Ruby Gems, it does not install the Node packages. Do note that I did many tests with Docker Compose and there is always that error and I have no clue why it's not working with Docker Compose but it's working with Docker. |
I am observing the same behavior with a very similar docker-compose.yml file for my Jekyll project. I tried building a custom image based on Ruby:3.0.2 with nodejs and npm installed explicitly, and with port 8124 exposed (not sure whether this is needed) and when attempting to run a container based on that image with docker-compose, am observing the same behavior as well. |
I get the same error running with the following
|
@olakara @guschiavon
|
I am running jekyll with jekyll-process through docker compose:
I keep getting error:
Any idea how to resolve this?
The text was updated successfully, but these errors were encountered: