diff options
| author | かひわし4（バージョン1） <khws4v1@gmail.com> | 2019-04-18 01:09:31 +0900 |
|---|---|---|
| committer | syuilo <Syuilotan@yahoo.co.jp> | 2019-04-18 01:09:31 +0900 |
| commit | 112a72abdfb78f8f6c76891e721029f4dc87d5c3 (patch) | |
| tree | 9b7982bf81e779da2a5584e5567d27036287dc11 /Dockerfile | |
| parent | Fix bug (diff) | |
| download | sharkey-112a72abdfb78f8f6c76891e721029f4dc87d5c3.tar.gz sharkey-112a72abdfb78f8f6c76891e721029f4dc87d5c3.tar.bz2 sharkey-112a72abdfb78f8f6c76891e721029f4dc87d5c3.zip | |
Docker: Back to npm from yarn (#4730)
This commit reverts "Fix Dockerfile #4214" which uses yarn instead of npm.
The cause of the build error is that binding.gyp and src/crypto_key.cc
are missing when installing dependencies.
In other words, yarn did not fix build error.
There is no reason to use yarn, so go back to npm.
Diffstat (limited to 'Dockerfile')
| -rw-r--r-- | Dockerfile | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/Dockerfile b/Dockerfile index ec7d8a6a27..be2768033d 100644 --- a/Dockerfile +++ b/Dockerfile @@ -21,12 +21,11 @@ RUN apk add --no-cache \ pkgconfig \ python \ zlib-dev -RUN npm i -g yarn COPY package.json ./ -RUN yarn install +RUN npm i COPY . ./ -RUN yarn build +RUN npm run build FROM base AS runner |