Closed claudio-viola closed 1 year ago
This 'hack' could be used to at least have the cache of docker file when we just bump package version and /or update test commands... There is another possible approach which would mean 'splitting' package files. https://stackoverflow.com/questions/51110793/bumping-package-json-version-without-invalidating-docker-cache
Hi, @claudio-viola @lewisdaly @elnyry-sam-k, can you please advise regarding the status of this issue?
PSB: Solution is to install dependencies locally MdB: only helps with local deploys, does not help with Docker; MdB does not have this issue.
@pedrosousabarreto and I agree that this can be resolved as per the following Dockerfile implementation in vNext: https://github.com/mojaloop/transfers-bc/blob/main/packages/command-handler-svc/Dockerfile
We must also ensure that librdkafka dependency is used for the "run-time" image instead of the development lib version librdkafka-dev (which could be used on the Builder image - if required).
I.e. the Dockerifle must contain the following:
RUN apk add --no-cache -t librdkafka
BUILD_LIBRDKAFKA=0
env parameter to skip the LIBRDKAFKA library build during the install:RUN BUILD_LIBRDKAFKA=0 npm install
Request:
Decision(s):
Follow-up:
Dependencies:
Accountability:
Notes: