#Failing to Build & Deploy Docker Compose on Portainer

6 messages · Page 1 of 1 (latest)

cobalt spruce
#
2024-03-27T17:37:05.827421092Z 2024/03/27 05:37PM WRN composeplugin/composeplugin.go:162 > docker compose command failed | error="exit status 17" error_output="failed to solve: process \"/bin/sh -c npm run build\" did not complete successfully: exit code: 134\n" output="#1 [twin_protocol internal] load build definition from Dockerfile\n#1 transferring dockerfile: 672B done\n#1 DONE 0.0s\n\n#2 [twin_protocol internal] load metadata for docker.io/library/node:lts\n#2 DONE 0.2s\n\n#3 [twin_protocol internal] load .dockerignore\n#3 transferring context: 67B done\n#3 DONE 0.0s\n\n#4 [twin_protocol base 1/3] FROM docker.io/library/node:lts@sha256:92e7cb9a504da73ee3b5aed35f984f64eb1d526d0d1d77605ca92ef526987c5d\n#4 resolve docker.io/library/node:lts@sha256:92e7cb9a504da73ee3b5aed35f984f64eb1d526d0d1d77605ca92ef526987c5d 0.0s done\n#4 DONE 0.0s\n\n#5 [twin_protocol internal] load build context\n#5 transferring context: 8.01MB 0.1s done\n#5 DONE 0.1s\n\n#6 [twin_protocol base 2/3] WORKDIR /app\n#6 CACHED\n\n#7 [twin_protocol base 3/3] COPY package.json ./\n#7 DONE 0.1s\n\n#8 [twin_protocol build-deps 1/1] RUN npm install --production=false\n#8 0.606 npm WARN config production Use `--omit=dev` instead.\n#8 ...\n\n#9 [twin_protocol prod-deps 1/1] RUN npm install --production\n#9 0.510 npm WARN config production Use `--omit=dev` instead.\n#9 68.40 npm WARN deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead\n#9 ...\n\n#8 [twin_protocol build-deps 1/1] RUN npm install --production=false\n#8 73.21 npm WARN deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead\n#8 ...\n\n#9 [twin_protocol prod-deps 1/1] RUN npm install --production\n#9 76.13 \n#9 76.13 added 669 packages, and audited 670 packages in 1m\n#9 76.13 \n#9 76.13 201 packages are looking for funding\n#9 76.13   run `npm fund` for details\n#9 76.13 \n#9 76.13 found 0 vulnerabilities\n#9 ...\n\n#8 [twin_protocol build-deps 1/1] RUN npm install --production=false\n#8 82.30 \n#8 82.30 added 1051 packages, and audited 1052 packages in 1m\n#8 82.30 \n#8 82.30 363 packages are looking for funding\n#8 82.30   run `npm fund` for details\n#8 82.31 \n#8 82.31 found 0 vulnerabilities\n#8 DONE 84.2s\n\n#9 [twin_protocol prod-deps 1/1] RUN npm install --production\n#9 DONE 84.2s\n\n#10 [twin_protocol build 1/2] COPY . .\n#10 DONE 0.1s\n\n#11 [twin_protocol build 2/2] RUN npm run build\n#11 0.589 \n#11 0.589 > [email protected] build\n#11 0.589 > astro check && astro build\n#11 0.589 \n#11 1.167 ▶ Astro collects anonymous usage data.\n#11 1.167   This information helps us improve Astro.\n#11 1.167   Run \"astro telemetry disable\" to opt-out.\n#11 1.167   https://astro.build/telemetry\n#11 1.167 \n#11 3.705 17:35:42 [vite] Forced re-optimization of dependencies\n#11 3.765 17:35:42 Types generated 136ms\n#11 3.775 17:35:42 [check] Getting diagnostics for Astro files in /app...\n#11 ...\n\n#12 [twin_protocol runtime 1/2] COPY --from=prod-deps /app/node_modules ./node_modules\n#12 DONE 4.0s\n\n#11 [twin_protocol build 2/2] RUN npm run build\n#11 45.38 \x1b[96mclient/_astro/App.Dtl6Fnr3.js\x1b[0m:\x1b[93m4136\x1b[0m:\x1b[93m21657\x1b[0m - \x1b[93mwarning\x1b[0m\x1b[90m ts(6133): \x1b[0m'e' is declared but its value is never read.\n#11 45.38 \n#11 45.38 \x1b[7m4136\x1b[0m `;`${BU}${zU}${$e.tonemapping_fragment}${$e.colorspace_fragment}`;for(let r=0;r<256;r++)(r<16?\"0\":\"\")+r.toString(16);var Tb={exports:{}};Tb.exports=fh;Tb.exports.default=fh;function fh(r,e,t){t=t
#

@feral pecan I'll put it here cause idk wassup

#

If I have a hybrid site with no server page enabled yet

#

Could that cause it for some reason?

#

okay my deploy script might have been keeping the server and client from the built version before

#

yay!