polarathene
commented
5 years ago Despite changes above I've provided, this only allows for getting libvips(vips-dev) to build. The npm sharp package will also build using it, but attempting to run the actual container with gatsby develop spouts a tonne of errors to do with the gatsby-plugin-sharp afaik. Building that seems to cause errors too..
This appears to be due to using the edge repositories for libvips. They're stated to not be reliable when used with non-edge versions of Alpine.. That'd explain why a similar Docker Image was building fine in the past but now also fails to build. The npm package sharp will install binaries if it doesn't detect a local libvips install on Alpine 3.8+ for nodejs v8 or v10.
I've recently got a Docker Image that actually builds and runs properly. I had success with this Dockerfile and removing the libvips dependency install, but for some reason couldn't connect over localhost:8000 to the running gatsby develop server. Not wanting to spend more time debugging why that is, I used a bit of the other linked Docker Image files which fixed that issue.
Dockerfile
FROM node:10-alpine
EXPOSE 8000
ARG GATSBY_VERSION=^2.0.0
# Install dev dependencies
RUN set -x \
&& apk add --no-cache \
g++ \
git \
make \
python2 \
binutils
# Install gatsby cli and cleanup
RUN set -x \
&& npm install --global gatsby@${GATSBY_VERSION} \
--no-optional gatsby@${GATSBY_VERSION} \
&& npm cache clean --force
RUN mkdir -p /site
WORKDIR /site
VOLUME /site
COPY ./entry.sh /
RUN chmod +x /entry.sh
ENTRYPOINT ["/entry.sh"]entry.sh
#!/bin/sh
set -e
export GATSBY_DIR="/site"
export PATH="$PATH:/usr/local/bin/gatsby"
# Initialize Gatsby or run NPM install if needed
if [ ! -f "$GATSBY_DIR/package.json" ]
then
echo "Initializing Gatsby..."
gatsby new $GATSBY_DIR
else
if [ ! -e "$GATSBY_DIR/node_modules/" ]
then
echo "Node modules is empty. Running npm install..."
npm install
fi
fi
# Decide what to do
if [ "$1" == "develop" ]
then
rm -rf $GATSBY_DIR/public
gatsby develop --host 0.0.0.0
elif [ "$1" == "build" ]
then
rm -rf $GATSBY_DIR/public
gatsby build
elif [ "$1" == "stage" ]
then
rm -rf $GATSBY_DIR/public
gatsby build
gatsby serve --port 8000
else
exec $@
fiBuild: docker build -t docker-gatsby .
Run: docker run -it --rm -v $(pwd)/site:/site -p 8000:8000 docker-gatsby develop
Maybe if I find some time to work on it a bit more I could make another PR. Just thought I'd share this as if you try building the current PR and using it now, I think you'll run into the problems I've been pointing out.
aslafy-z
Closes #16 #11
node:10-alpineBuild with:
Works best with a volume:
User is specified to ensure it doesn't fucked up your files permission.
Supported commands:
develop->gatsby developbuild->gatsby buildserve->gatsby servestage->gatsby build && gatsby serveThese commands need to have wrappers because they don't support configuration of host and port via variables environments. Too bad :(
You can also use others commands of
gatsbywhich does not need a wrapper (eg.:repl,new,info).If a folder without
package.jsonfile is mounted on the/sitedir, it will be provisioned with https://github.com/gatsbyjs/gatsby-starter-default.