You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
Describe the bug
If I use
RUN npm ci
in the base docker file, the generated docker file for the base image contains
RUN npm install
To Reproduce
Create a base dockerfile with
FROM node:16-alpine3.15 as base
WORKDIR /app
COPY ./package.json ./
COPY ./package-lock.json ./
RUN npm ci
Expected behavior
The generated docker file looks like
FROM node:16-alpine3.15 as base
WORKDIR /app
COPY ./package.json ./
COPY ./package-lock.json ./
RUN npm ci
Additional context
This is a problem because the install is overwriting the package-lock.json in side the docker image. Dosnt seem to happen in the template docker files only when used in the base. Im using V1.0.1
The text was updated successfully, but these errors were encountered:
Describe the bug
If I use
RUN npm ci
in the base docker file, the generated docker file for the base image contains
RUN npm install
To Reproduce
Create a base dockerfile with
FROM node:16-alpine3.15 as base
WORKDIR /app
COPY ./package.json ./
COPY ./package-lock.json ./
RUN npm ci
Expected behavior
The generated docker file looks like
FROM node:16-alpine3.15 as base
WORKDIR /app
COPY ./package.json ./
COPY ./package-lock.json ./
RUN npm ci
Additional context
This is a problem because the install is overwriting the package-lock.json in side the docker image. Dosnt seem to happen in the template docker files only when used in the base. Im using V1.0.1
The text was updated successfully, but these errors were encountered: