Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

errors during docker build #24

Open
rkl-mcguire opened this issue Mar 28, 2023 · 0 comments
Open

errors during docker build #24

rkl-mcguire opened this issue Mar 28, 2023 · 0 comments

Comments

@rkl-mcguire
Copy link

root@MyServer:/home/UserName/ServiceNow-DUO-Push-UI-Action# sudo docker build -t duoauth:1.0.0 .
[+] Building 24.9s (9/10)
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 456B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 1.89kB 0.0s
=> [internal] load metadata for docker.io/library/node:latest 0.6s
=> [1/6] FROM docker.io/library/node@sha256:1fab548e95c779df229e4b50d8d2 0.0s
=> [internal] load build context 0.2s
=> => transferring context: 9.89MB 0.2s
=> CACHED [2/6] WORKDIR /home/node 0.0s
=> CACHED [3/6] RUN mkdir /home/node/.npm-global 0.0s
=> [4/6] ADD . /home/node 0.1s
=> ERROR [5/6] RUN cd /home/node && npm install 24.0s

[5/6] RUN cd /home/node && npm install:
#0 1.034 npm WARN old lockfile
#0 1.034 npm WARN old lockfile The package-lock.json file was created with an old version of npm,
#0 1.035 npm WARN old lockfile so supplemental metadata must be fetched from the registry.
#0 1.036 npm WARN old lockfile
#0 1.037 npm WARN old lockfile This is a one-time fix-up, please be patient...
#0 1.037 npm WARN old lockfile
#0 16.82 npm WARN EBADENGINE Unsupported engine {
#0 16.82 npm WARN EBADENGINE package: 'duo-button@0.0.0',
#0 16.82 npm WARN EBADENGINE required: { node: '^10.0.0', npm: '>= 3.0.0' },
#0 16.82 npm WARN EBADENGINE current: { node: 'v19.8.1', npm: '9.5.1' }
#0 16.82 npm WARN EBADENGINE }
#0 19.39 npm WARN deprecated xmldom@0.2.1: Deprecated due to CVE-2021-21366 resolved in 0.5.0
#0 19.70 npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
#0 20.24 npm WARN deprecated ini@1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue
#0 20.37 npm WARN deprecated har-validator@5.1.3: this library is no longer supported
#0 20.56 npm WARN deprecated flat@4.1.0: Fixed a prototype pollution security issue in 4.1.0, please upgrade to ^4.1.1 or ^5.0.1.
#0 20.58 npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
#0 20.77 npm WARN deprecated request@2.88.2: request has been deprecated, see request/request#3142
#0 21.19 npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
#0 21.37 npm WARN deprecated feathers-sequelize@6.1.0: Upgrade to feathers-sequelize 6.3.3 or later for important security and dependency updates
#0 21.67 npm WARN deprecated axios@0.19.2: Critical security vulnerability fixed in v0.21.1. For more information, see axios/axios#3410
#0 22.11 npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
#0 22.13 npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
#0 22.44 npm WARN deprecated sequelize@5.21.5: Please update to v6 or higher! A migration guide can be found here: https://sequelize.org/v6/manual/upgrade-to-v6.html
#0 23.91 npm notice
#0 23.91 npm notice New minor version of npm available! 9.5.1 -> 9.6.2
#0 23.91 npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.6.2
#0 23.91 npm notice Run npm install -g npm@9.6.2 to update!
#0 23.91 npm notice
#0 23.91 npm ERR! code EACCES
#0 23.91 npm ERR! syscall open
#0 23.91 npm ERR! path /home/node/package-lock.json
#0 23.91 npm ERR! errno -13
#0 23.91 npm ERR! Error: EACCES: permission denied, open '/home/node/package-lock.json'
#0 23.91 npm ERR! [Error: EACCES: permission denied, open '/home/node/package-lock.json'] {
#0 23.91 npm ERR! errno: -13,
#0 23.91 npm ERR! code: 'EACCES',
#0 23.91 npm ERR! syscall: 'open',
#0 23.91 npm ERR! path: '/home/node/package-lock.json'
#0 23.91 npm ERR! }
#0 23.91 npm ERR!
#0 23.92 npm ERR! The operation was rejected by your operating system.
#0 23.92 npm ERR! It is likely you do not have the permissions to access this file as the current user
#0 23.92 npm ERR!
#0 23.92 npm ERR! If you believe this might be a permissions issue, please double-check the
#0 23.92 npm ERR! permissions of the file and its containing directories, or try running
#0 23.92 npm ERR! the command again as root/Administrator.
#0 23.92
#0 23.92 npm ERR! A complete log of this run can be found in:
#0 23.92 npm ERR! /home/node/.npm/_logs/2023-03-28T13_52_00_601Z-debug-0.log


Dockerfile:18

16 | ADD . /home/node
17 |
18 | >>> RUN cd /home/node && npm install
19 |
20 | #CMD npm install /home/node/app

ERROR: failed to solve: process "/bin/sh -c cd /home/node && npm install" did not complete successfully: exit code: 243
root@MyServer:/home/UserName/ServiceNow-DUO-Push-UI-Action#
=====================================================
I ran these commands:
sudo apt update
sudo apt install nodejs npm
npm install
npm audit fix --force
git add package-lock.json
git commit -m "update package-lock.json

Reran the docker build and the results did not change. The docker setup continues to fail.
Note: the log file: /home/node/.npm/_logs/2023-03-28T13_52_00_601Z-debug-0.log
Does not get created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant