github/probly
1
1
Fork 0
mirror of https://github.com/PragmaticMachineLearning/probly.git synced 2026-01-11 14:28:01 -05:00
Code Issues 2 Packages Projects Releases Wiki Activity

docker-compose fails to build #16

New Issue
Closed
opened 2025-07-08 08:36:46 -04:00 by AtHeartEngineer · 0 comments
AtHeartEngineer commented 2025-07-08 08:36:46 -04:00
Owner
Copy Link

Originally created by @atomi on 2/28/2025

Error from cli

probly main (6f7d8dfb) took 9s 
✗ docker-compose build
[+] Building 1.0s (12/20)                                                                                                  docker:default
 => [probly internal] load build definition from Dockerfile                                                                          0.0s
 => => transferring dockerfile: 1.38kB                                                                                               0.0s
 => [probly internal] load metadata for docker.io/library/node:20-alpine                                                             0.2s
 => [probly internal] load .dockerignore                                                                                             0.0s
 => => transferring context: 2B                                                                                                      0.0s
 => [probly internal] load build context                                                                                             0.0s
 => => transferring context: 5.03kB                                                                                                  0.0s
 => [probly base 1/1] FROM docker.io/library/node:20-alpine@sha256:053c1d99e608fe9fa0db6821edd84276277c0a663cd181f4a3e59ee20f5f07ea  0.0s
 => CACHED [probly deps 1/4] WORKDIR /app                                                                                            0.0s
 => CACHED [probly runner 2/8] RUN addgroup --system --gid 1001 nodejs                                                               0.0s
 => CACHED [probly runner 3/8] RUN adduser --system --uid 1001 nextjs                                                                0.0s
 => CACHED [probly runner 4/8] RUN mkdir -p ./public                                                                                 0.0s
 => CACHED [probly runner 5/8] RUN chown -R nextjs:nodejs ./public                                                                   0.0s
 => CACHED [probly deps 2/4] COPY package.json package-lock.json* ./                                                                 0.0s
 => ERROR [probly deps 3/4] RUN npm ci                                                                                               0.8s
------
 > [probly deps 3/4] RUN npm ci:
0.757 npm error code EUSAGE
0.757 npm error
0.757 npm error The `npm ci` command can only install with an existing package-lock.json or
0.757 npm error npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
0.757 npm error later to generate a package-lock.json file, then try again.
0.757 npm error
0.757 npm error Clean install a project
0.757 npm error
0.757 npm error Usage:
0.757 npm error npm ci
0.757 npm error
0.757 npm error Options:
0.757 npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
0.757 npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
0.757 npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]
0.757 npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]
0.757 npm error [--no-bin-links] [--no-fund] [--dry-run]
0.757 npm error [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
0.757 npm error [-ws|--workspaces] [--include-workspace-root] [--install-links]
0.757 npm error
0.757 npm error aliases: clean-install, ic, install-clean, isntall-clean
0.757 npm error
0.757 npm error Run "npm help ci" for more info
0.759 npm error A complete log of this run can be found in: /root/.npm/_logs/2025-02-28T21_42_57_804Z-debug-0.log
------
failed to solve: process "/bin/sh -c npm ci" did not complete successfully: exit code: 1
*Originally created by @atomi on 2/28/2025* Error from cli ``` probly main (6f7d8dfb) took 9s ✗ docker-compose build [+] Building 1.0s (12/20) docker:default => [probly internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 1.38kB 0.0s => [probly internal] load metadata for docker.io/library/node:20-alpine 0.2s => [probly internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [probly internal] load build context 0.0s => => transferring context: 5.03kB 0.0s => [probly base 1/1] FROM docker.io/library/node:20-alpine@sha256:053c1d99e608fe9fa0db6821edd84276277c0a663cd181f4a3e59ee20f5f07ea 0.0s => CACHED [probly deps 1/4] WORKDIR /app 0.0s => CACHED [probly runner 2/8] RUN addgroup --system --gid 1001 nodejs 0.0s => CACHED [probly runner 3/8] RUN adduser --system --uid 1001 nextjs 0.0s => CACHED [probly runner 4/8] RUN mkdir -p ./public 0.0s => CACHED [probly runner 5/8] RUN chown -R nextjs:nodejs ./public 0.0s => CACHED [probly deps 2/4] COPY package.json package-lock.json* ./ 0.0s => ERROR [probly deps 3/4] RUN npm ci 0.8s ------ > [probly deps 3/4] RUN npm ci: 0.757 npm error code EUSAGE 0.757 npm error 0.757 npm error The `npm ci` command can only install with an existing package-lock.json or 0.757 npm error npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or 0.757 npm error later to generate a package-lock.json file, then try again. 0.757 npm error 0.757 npm error Clean install a project 0.757 npm error 0.757 npm error Usage: 0.757 npm error npm ci 0.757 npm error 0.757 npm error Options: 0.757 npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling] 0.757 npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]] 0.757 npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]] 0.757 npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit] 0.757 npm error [--no-bin-links] [--no-fund] [--dry-run] 0.757 npm error [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]] 0.757 npm error [-ws|--workspaces] [--include-workspace-root] [--install-links] 0.757 npm error 0.757 npm error aliases: clean-install, ic, install-clean, isntall-clean 0.757 npm error 0.757 npm error Run "npm help ci" for more info 0.759 npm error A complete log of this run can be found in: /root/.npm/_logs/2025-02-28T21_42_57_804Z-debug-0.log ------ failed to solve: process "/bin/sh -c npm ci" did not complete successfully: exit code: 1 ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
AtHeartEngineer
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/probly#16
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?