locally running the Frontend fails, in docker and natively.
- Dominant language
- Python
- Stars
- 30
- Forks
- 37
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 19
Description
trying to run the frontend using `make be` or `docker-compose up frontend` both fail with this.
```
[+] Building 3.3s (9/11) docker:default
=> [frontend internal] load .dockerignore 0.1s
=> => transferring context: 321B 0.0s
=> [frontend internal] load build definition from Dockerfile 0.1s
=> => transferring dockerfile: 262B 0.0s
=> [frontend internal] load metadata for docker.io/library/node:14.21.3 1.7s
=> [frontend auth] library/node:pull token for registry-1.docker.io 0.0s
=> CANCELED [frontend 1/6] FROM docker.io/library/node:14.21.3@sha256:a158d3b9b4e3fa813fa6c8c590b8f0a860e015ad4e59bbce5744d2f6fd8461aa 0.7s
=> => resolve docker.io/library/node:14.21.3@sha256:a158d3b9b4e3fa813fa6c8c590b8f0a860e015ad4e59bbce5744d2f6fd8461aa 0.1s
=> => sha256:3d2201bd995cccf12851a50820de03d34a17011dcbb9ac9fdf3a50c952cbb131 0B / 10.00MB 1.4s
=> => sha256:a158d3b9b4e3fa813fa6c8c590b8f0a860e015ad4e59bbce5744d2f6fd8461aa 776B / 776B 0.0s
=> => sha256:2cafa3fbb0b6529ee4726b4f599ec27ee557ea3dea7019182323b3779959927f 2.21kB / 2.21kB 0.0s
=> => sha256:1d12470fa662a2a5cb50378dcdc8ea228c1735747db410bbefb8e2d9144b5452 7.51kB / 7.51kB 0.0s
=> => sha256:2ff1d7c41c74a25258bfa6f0b8adb0a727f84518f55f65ca845ebc747976c408 0B / 50.45MB 1.4s
=> => sha256:b253aeafeaa7e0671bb60008df01de101a38a045ff7bc656e3b0fbfc7c05cca5 0B / 7.86MB 1.4s
=> [frontend internal] load build context 0.6s
=> => transferring context: 123.94kB 0.5s
=> CACHED [frontend 2/6] RUN mkdir /app 0.0s
=> CACHED [frontend 3/6] WORKDIR /app 0.0s
=> ERROR [frontend 4/6] COPY package.json package-lock.json ./ 0.0s
------
> [frontend 4/6] COPY package.json package-lock.json ./:
------
failed to solve: failed to compute cache key: failed to calculate checksum of ref ac903f2d-9d8e-488d-860e-652f0c296625::gf1w56qlhz3pzb4i197yla7yh: "/package-lock.json": not found
```
and attempting to run it natively with `npm` (node 14.21.3 and npm version 6.14.18) and `yarn install` gives me this.
```
➤ YN0000: └ Completed in 1s 450ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ @fortawesome/fontawesome-common-types@npm:6.4.2::__archiveUrl=https%3A%2F%2Fnpm.fontawesome.com%2F%40fortawesome%2Ffontawesome-common-types%2F-%2F6.4.2%2Ffontawesome-common-types-6.4.2.tgz can't be found in the cache and will be fetched from the remote server
➤ YN0013: │ @fortawesome/fontawesome-pro@npm:6.4.2::__archiveUrl=https%3A%2F%2Fnpm.fontawesome.com%2F%40fortawesome%2Ffontawesome-pro%2F-%2F6.4.2%2Ffontawesome-pro-6.4.2.tgz can't be found in the cache and will be fetched from the remote server
➤ YN0013: │ @fortawesome/fontawesome-svg-core@npm:6.4.2::__archiveUrl=https%3A%2F%2Fnpm.fontawesome.com%2F%40fortawesome%2Ffontawesome-svg-core%2F-%2F6.4.2%2Ffontawesome-svg-core-6.4.2.tgz can't be found in the cache and will be fetched from the remote server
➤ YN0013: │ @fortawesome/pro-light-svg-icons@npm:6.4.2::__archiveUrl=https%3A%2F%2Fnpm.fontawesome.com%2F%40fortawesome%2Fpro-light-svg-icons%2F-%2F6.4.2%2Fpro-light-svg-icons-6.4.2.tgz can't be found in the cache and will be fetched from the remote server
➤ YN0013: │ @fortawesome/react-fontawesome@npm:0.2.0::__archiveUrl=https%3A%2F%2Fnpm.fontawesome.com%2F%40fortawesome%2Freact-fontawesome%2F-%2F0.2.0%2Freact-fontawesome-0.2.0.tgz can't be found in the cache and will be fetched from the remote server
➤ YN0041: │ @fortawesome/fontawesome-svg-core@npm:6.4.2::__archiveUrl=https%3A%2F%2Fnpm.fontawesome.com%2F%40fortawesome%2Ffontawesome-svg-core%2F-%2F6.4.2%2Ffontawesome-svg-core-6.4.2.tgz: Invalid authentication (as an anonymous user)
➤ YN0041: │ @fortawesome/fontawesome-pro@npm:6.4.2::__archiveUrl=https%3A%2F%2Fnpm.fontawesome.com%2F%40fortawesome%2Ffontawesome-pro%2F-%2F6.4.2%2Ffontawesome-pro-6.4.2.tgz: Invalid authentication (as an anonymous user)
➤ YN0041: │ @fortawesome/react-fontawesome@npm:0.2.0::__archiveUrl=https%3A%2F%2Fnpm.fontawesome.com%2F%40fortawesome%2Freact-fontawesome%2F-%2F0.2.0%2Freact-fontawesome-0.2.0.tgz: Invalid authentication (as an anonymous user)
➤ YN0041: │ @fortawesome/pro-light-svg-icons@npm:6.4.2::__archiveUrl=https%3A%2F%2Fnpm.fontawesome.com%2F%40fortawesome%2Fpro-light-svg-icons%2F-%2F6.4.2%2Fpro-light-svg-icons-6.4.2.tgz: Invalid authentication (as an anonymous user)
➤ YN0041: │ @fortawesome/fontawesome-common-types@npm:6.4.2::__archiveUrl=https%3A%2F%2Fnpm.fontawesome.com%2F%40fortawesome%2Ffontawesome-common-types%2F-%2F6.4.2%2Ffontawesome-common-types-6.4.2.tgz: Invalid authentication (as an anonymous user)
➤ YN0000: └ Completed in 3s 817ms
➤ YN0000: Failed with errors in 5s 282ms
```
Contributor guide
Research direction
Start with the frontend Dockerfile and the package.json/package-lock.json files referenced by the Docker build, then reproduce the failure with `make be` or `docker-compose up frontend`. Check the native `npm` or `yarn install` output and the Font Awesome package configuration. Done means the frontend can install dependencies and run both natively and through Docker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript, node.js
- Domain
- build-system, devops, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100