4 ms·
I've been using the official Docker image for Jekyll (https://hub.docker.com/r/jekyll/jekyll/ https://hub.docker.com/r/jekyll/jekyll/), which makes it fairly ea
by dguo 10y ago
I've been using the official Docker image for Jekyll (https://hub.docker.com/r/jekyll/jekyll/ https://hub.docker.com/r/jekyll/jekyll/), which makes it fairly easy to avoid this particular problem. Assuming you're willing/able to have a dependency on Docker.
- andmarios 10y agoI am all for docker, we use it on production and I maintain a couple docker github repos. But docker also has its own complexities. A user that can run docker, is almost as good as a user with sudo rights. Would you give your CI system root access on your server? There are of course workarounds, like permit the CI system to run only the jekyll image by adjusting the sudoers file but, at some point you have to think about the scope of configuration needed for deploying your site. Also docker on hardened servers can be challenging, for example I had to disable most of grsecurity's chroot protections to have docker run.