Fixing dependency issues that arise in the docker image.#601
Conversation
The dockerfile didn't previously copy in the package-lock file which means package dependency issues could occasionally arise. This is fixed by simply copying in the package-lock file.
|
|
@mcottontensor Look's good to me. Does this need a changeset? Wdyt? |
|
Nah no real change just a fixed config. |
mcottontensor
added
auto-backport
The dockerfile didn't previously copy in the package-lock file which means package dependency issues could occasionally arise. This is fixed by simply copying in the package-lock file. (cherry picked from commit ca62a87)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
…602) The dockerfile didn't previously copy in the package-lock file which means package dependency issues could occasionally arise. This is fixed by simply copying in the package-lock file. (cherry picked from commit ca62a87) Co-authored-by: mcottontensor <80377552+mcottontensor@users.noreply.github.com>
2 participants
Relevant components:
Problem statement:
Occasionally when building the signalling docker image, package issues could randomly show up.
Solution
This was simply caused by the fact that the package-lock file was not copied into the image. This change copies that file in which locks the packages to known working configurations.