Closed webpigeon closed 6 years ago
short term fix:
Remote into the docker container as root:
docker exec -u 0 -it realms-wiki /bin/bash
install clean-css from npm
npm install -g clean-css
Refreshing the page in the web browser then results in the realms wiki page (all be it without icons) and some javascript errors - it seems to be trying to load stuff from file paths rather than relative to the url in the stylesheet:
@font-face {
font-family:'Glyphicons Halflings';
src:url(/home/wiki/realms-wiki/realms/static/vendor/bootswatch-dist/fonts/glyphicons-halflings-regular.eot);
src:url(/home/wiki/realms-wiki/realms/static/vendor/bootswatch-dist/fonts/glyphicons-halflings-regular.eot?#iefix) format('embedded-opentype'),url(/home/wiki/realms-wiki/realms/static/vendor/bootswatch-dist/fonts/glyphicons-halflings-regular.woff2) format('woff2'),url(/home/wiki/realms-wiki/realms/static/vendor/bootswatch-dist/fonts/glyphicons-halflings-regular.woff) format('woff'),url(/home/wiki/realms-wiki/realms/static/vendor/bootswatch-dist/fonts/glyphicons-halflings-regular.ttf) format('truetype'),url(/home/wiki/realms-wiki/realms/static/vendor/bootswatch-dist/fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular) format('svg')
}
I'm guessing that chaging line 9 of the dockerfile from:
npm install -g bower
to
npm install -g bower clean-css
might fix the missing cleancss problem
Indeed, I had the same issue and went ahead to solve it: PR #175
pulled #175
I can confim. The issue is still present and can be reproduced by:
docker run --name realms-wiki -p 5000:5000 -d realms/realms-wiki
This is still happening.
Sorry about this. I am confirming the docker image is busted. I have done some work on a new one that will be automatically updated on commit. There is an issue that requires some code changes as well.
Hello scragg0x, THX for the short info. It is definitively a nice piece of code. Thumbs up!
Was this ever resolved? I am still running into the Internal Server Error message even after trying the steps listed above.
Here is my output:
[roycepope:~]$ docker run --name realms-wiki -p 5000:5000 -d realms/realms-wiki ccf51c85ea7b94728cbe9a12ba4fb12724f2b0e7a4e72d562a6e01fcf0375877
[roycepope:~]$ docker exec -u 0 -it realms-wiki /bin/bash
root@ccf51c85ea7b:/home/wiki/realms-wiki# npm install -g clean-css npm http GET https://registry.npmjs.org/clean-css npm http 200 https://registry.npmjs.org/clean-css npm http GET https://registry.npmjs.org/clean-css/-/clean-css-4.1.1.tgz npm http 200 https://registry.npmjs.org/clean-css/-/clean-css-4.1.1.tgz npm WARN engine clean-css@4.1.1: wanted: {"node":">= 4.0"} (current: {"node":"v0.10.25","npm":"1.3.10"}) npm http GET https://registry.npmjs.org/source-map npm http 200 https://registry.npmjs.org/source-map npm http GET https://registry.npmjs.org/source-map/-/source-map-0.5.6.tgz npm http 200 https://registry.npmjs.org/source-map/-/source-map-0.5.6.tgz clean-css@4.1.1 /usr/local/lib/node_modules/clean-css └── source-map@0.5.6
root@ccf51c85ea7b:/home/wiki/realms-wiki# exit
that did the trick!
Is it possible to get a push of the docker image? the fix from the recent commits don't appear to have been updates in the docker repo.
Should be resolved, try the latest docker image
Hello,
The docker instance now boots, which is good news :), however, upon visiting the page in the browser (http://servername:5000) I am greeted with a 500 error.
docker logs realms-wiki
shows the following:The steps used to create the docker container are: