Warnings during `make docker`
Closed this issue · 6 comments
richb-hanover commented
Question
Thanks for creating vitejs-docker-dev! I wish something like this had existed years ago! (I inherited an old project with a gazillion outdated dependencies. It was a hassle even to get something to compile. Had they used a Docker container from day one, it would have made it way easier to make it current...)
The vitejs-docker-dev instance built and operated just fine. I was able to edit the Vite app source files (in /app) and changes were immediately reflected as desired.
But... I noticed a few warnings when running make docker though. Here's an example:
WARN "postinstall" script of "test-ssr-deps@0.0.0" inside "/app/vite/packages/playground/ssr-deps" is skipped as the working directory seems suspicious. To run this lifecycle script anyway, use "--unsafe-perm".
I'm new to Vitejs: Are these important? What could I do to eliminate them? Many thanks.
Additional context
Here's a display of the entire make docker output:
√ github % git clone https://github.com/nystudio107/vitejs-docker-dev.git
Cloning into 'vitejs-docker-dev'...
remote: Enumerating objects: 169, done.
remote: Counting objects: 100% (169/169), done.
remote: Compressing objects: 100% (115/115), done.
remote: Total 169 (delta 80), reused 138 (delta 49), pack-reused 0
Receiving objects: 100% (169/169), 498.69 KiB | 3.14 MiB/s, done.
Resolving deltas: 100% (80/80), done.
√ github % cd vitejs-docker-dev
√ vitejs-docker-dev % make docker
docker build \
docker-config/ \
-t nystudio107/vitejs-dev:16-alpine \
--build-arg TAG=16-alpine \
--no-cache
[+] Building 44.5s (8/8) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 564B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 82B 0.0s
=> [internal] load metadata for docker.io/library/node:16-alpine 1.2s
=> [auth] library/node:pull token for registry-1.docker.io 0.0s
=> [1/3] FROM docker.io/library/node:16-alpine@sha256:da7ef512955c906b6fa84a02295a56d0172b2eb57e09286ec7abc02cfbb4 13.0s
=> => resolve docker.io/library/node:16-alpine@sha256:da7ef512955c906b6fa84a02295a56d0172b2eb57e09286ec7abc02cfbb4c 0.0s
=> => sha256:53f011c818d294979f7179495b04ebbe0ec6152a84e491b55174bad783131412 1.16kB / 1.16kB 0.0s
=> => sha256:633ac691384c298ecd9821ac305817ce6f47dcd24260b3260a237cc021a6815c 6.58kB / 6.58kB 0.0s
=> => sha256:1ef6f24acb8cd5a1bab27c1d78a085516c00e9289f69868bc6a691870be81b5c 35.40MB / 35.40MB 10.6s
=> => sha256:cce98d98dea35505e0b4f23abbc1cc3355971e1750546ffadec20f61a6669ead 2.34MB / 2.34MB 1.5s
=> => sha256:402b4d5fa115fb022a2f7e10cc5f8d4394bcf90eab55bb779bc3a020bcb4f52b 453B / 453B 0.7s
=> => sha256:da7ef512955c906b6fa84a02295a56d0172b2eb57e09286ec7abc02cfbb4c726 1.43kB / 1.43kB 0.0s
=> => extracting sha256:1ef6f24acb8cd5a1bab27c1d78a085516c00e9289f69868bc6a691870be81b5c 1.8s
=> => extracting sha256:cce98d98dea35505e0b4f23abbc1cc3355971e1750546ffadec20f61a6669ead 0.2s
=> => extracting sha256:402b4d5fa115fb022a2f7e10cc5f8d4394bcf90eab55bb779bc3a020bcb4f52b 0.0s
=> [2/3] WORKDIR /app 0.2s
=> [3/3] RUN set -eux; apk add --no-cache git python3 make g++ && rm - 28.3s
=> exporting to image 1.8s
=> => exporting layers 1.8s
=> => writing image sha256:653ce1e9460412b7697cb027441f73b0f8565624dcca83b3348b8387b4cc3e84 0.0s
=> => naming to docker.io/nystudio107/vitejs-dev:16-alpine 0.0s
docker container run \
--name vitejs-build-dev \
--rm \
-t \
-v "/Users/richb/github/vitejs-docker-dev":/app \
-e VITE_REPO=https://github.com/vitejs/vite.git \
-e VITE_DIR=vite \
-e APP_DIR=app \
nystudio107/vitejs-dev:16-alpine \
docker-config/docker.sh
Cloning into 'vite'...
remote: Enumerating objects: 34791, done.
remote: Counting objects: 100% (9/9), done.
remote: Compressing objects: 100% (8/8), done.
remote: Total 34791 (delta 1), reused 9 (delta 1), pack-reused 34782
Receiving objects: 100% (34791/34791), 16.31 MiB | 3.29 MiB/s, done.
Resolving deltas: 100% (24446/24446), done.
Updating files: 100% (1105/1105), done.
Scope: all 101 workspace projects
../.. | +1155 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Packages are hard linked from the content-addressable store to the virtual store.
Content-addressable store is at: /app/.pnpm-store/v3
Virtual store is at: ../../node_modules/.pnpm
Downloading registry.npmjs.org/typescript/4.5.4: 11.3 MB/11.3 MB, done
../.. | Progress: resolved 1155, reused 0, downloaded 1150, added 1155, done
../../node_modules/.pnpm/core-js@3.21.1/node_modules/core-js: Running postinstall script, done in 152ms
../../node_modules/.pnpm/bcrypt@5.0.1/node_modules/bcrypt: Running install script, done in 1.6s
../../node_modules/.pnpm/node-cron@2.0.3/node_modules/node-cron: Running postinstall script, done in 121ms
../../node_modules/.pnpm/simple-git-hooks@2.7.0/node_modules/simple-git-hooks: Running postinstall script, done in 177ms
../../node_modules/.pnpm/esbuild@0.14.27/node_modules/esbuild: Running postinstall script, done in 140ms
../../node_modules/.pnpm/playwright-chromium@1.20.1/node_modules/playwright-chromium: Running install script, done in 56.1s
dependencies:
+ esbuild 0.14.27
+ postcss 8.4.12
+ resolve 1.22.0
+ rollup 2.62.0
devDependencies:
+ @ampproject/remapping 2.1.2
+ @babel/parser 7.17.8
+ @babel/types 7.17.0
+ @jridgewell/trace-mapping 0.3.4
+ @rollup/plugin-alias 3.1.9
+ @rollup/plugin-commonjs 21.0.3
+ @rollup/plugin-dynamic-import-vars 1.4.2
+ @rollup/plugin-json 4.1.0
+ @rollup/plugin-node-resolve 13.1.3
+ @rollup/plugin-typescript 8.3.1
+ @rollup/pluginutils 4.2.0
+ @types/convert-source-map 1.5.2
+ @types/cross-spawn 6.0.2
+ @types/debug 4.1.7
+ @types/estree 0.0.51
+ @types/etag 1.8.1
+ @types/less 3.0.3
+ @types/micromatch 4.0.2
+ @types/mime 2.0.3
+ @types/node 16.11.26
+ @types/resolve 1.20.1
+ @types/sass 1.43.1
+ @types/stylus 0.48.36
+ @types/ws 8.5.3
+ @vue/compiler-dom 3.2.31
+ acorn 8.7.0
+ cac 6.7.9
+ chokidar 3.5.3
+ connect 3.7.0
+ connect-history-api-fallback 1.6.0
+ convert-source-map 1.8.0
+ cors 2.8.5
+ cross-spawn 7.0.3
+ debug 4.3.4
+ dotenv 14.3.2
+ dotenv-expand 5.1.0
+ es-module-lexer 0.10.4
+ estree-walker 2.0.2
+ etag 1.8.1
+ fast-glob 3.2.11
+ http-proxy 1.18.1
+ json5 2.2.1
+ launch-editor-middleware 2.3.0
+ magic-string 0.26.1
+ micromatch 4.0.5
+ mrmime 1.0.0
+ node-forge 1.3.0
+ okie 1.0.1
+ open 8.4.0
+ periscopic 2.0.3
+ picocolors 1.0.0
+ postcss-import 14.1.0
+ postcss-load-config 3.1.3
+ postcss-modules 4.3.1
+ resolve.exports 1.1.0
+ rollup-plugin-license 2.6.1
+ sirv 2.0.2
+ source-map-js 1.0.2
+ source-map-support 0.5.21
+ strip-ansi 6.0.1
+ terser 5.12.1
+ tsconfck 1.2.1
+ tslib 2.3.1
+ types <- types
+ ws 8.5.0
../playground/alias postinstall$ ts-node ../../../scripts/patchFileDeps.ts
└─ Running...
../playground/optimize-deps postinstall$ ts-node ../../../scripts/patchFileDeps.ts
└─ Running...
../playground/ssr-deps postinstall$ ts-node ../../../scripts/patchFileDeps.ts
└─ Running...
WARN "postinstall" script of "test-ssr-deps@0.0.0" inside "/app/vite/packages/playground/ssr-deps" is skipped as the working directory seems suspicious. To run this lifecycle script anyway, use "--unsafe-perm".
WARN "postinstall" script of "test-optimize-deps@0.0.0" inside "/app/vite/packages/playground/optimize-deps" is skipped as the working directory seems suspicious. To run this lifecycle script anyway, use "--unsafe-perm".
WARN "postinstall" script of "test-alias@0.0.0" inside "/app/vite/packages/playground/alias" is skipped as the working directory seems suspicious. To run this lifecycle script anyway, use "--unsafe-perm".
../playground/optimize-missing-deps postinstall$ ts-node ../../../scripts/patchFileDeps.ts
└─ Running...
WARN "postinstall" script of "optimize-missing-deps@0.0.0" inside "/app/vite/packages/playground/optimize-missing-deps" is skipped as the working directory seems suspicious. To run this lifecycle script anyway, use "--unsafe-perm".
Packages: +1
+
Downloading registry.npmjs.org/typescript/4.6.3: 11.4 MB/11.4 MB, done
Packages are hard linked from the content-addressable store to the virtual store.
Content-addressable store is at: /app/.pnpm-store/v3
Virtual store is at: node_modules/.pnpm
devDependencies:
+ typescript 4.6.3
Progress: resolved 1, reused 0, downloaded 1, added 1, done
√ vitejs-docker-dev %
khalwat commented
I'm not sure of the answer tbh -- I'd suggest posting it on the Vite repository, as I don't think it's specific to vite-docker-dev
richb-hanover commented
OK. I'll ask over at the Vitejs site and post any response I receive. Thanks!
richb-hanover commented
Update: These don't seem important - see the responses at vitejs/vite#7503 - I am content to leave this closed.
richb-hanover commented
@khalwat PS I really like this project. I mentioned it on my blog: https://randomneuronsfiring.com/migrating-snowpack-to-vite-and-docker/ (Let me know if I am missing anything important...) Thanks!
khalwat commented
Very cool @richb-hanover -- the article you linked to from there looks similar to my Dock Life writeup -> https://nystudio107.com/blog/dock-life-using-docker-for-all-the-things
richb-hanover commented
I added a link to your post. Thanks!