forked from mitre-attack/attack-navigator
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathDockerfile
32 lines (21 loc) · 879 Bytes
/
Dockerfile
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
# Build stage
FROM node:18
ENV NODE_OPTIONS=--openssl-legacy-provider
WORKDIR /src
# copy over needed files
COPY nav-app/ /src/nav-app/
COPY layers/*.md /src/layers/
COPY *.md /src/
WORKDIR /src/nav-app
# give user permissions
RUN chown -R node:node ./
# install packages and build
RUN npm install --unsafe-perm --legacy-peer-deps
# NOTE on legacy-peer-deps:
# The --legacy-peer-deps flags is included to bypass the dependency peer resolution conflict that arises between Angular
# and @angular-devkit/build-angular@0.1100.7, the latter of which has peerDependency: karma: '~5.1.0'. However,
# upgrading karma to 5.1.0 cascades into a litany of other dependency conflicts, which would ultimately require us to
# upgrade from Angular v11 to v12. Therefore, legacy-peer-deps will be allowed until a major framework upgrade can occur
EXPOSE 4200
CMD npm start
USER node