Attu dockerimage shouldn't call npm registry during runtime

[aashishsingh2803]

Describe the bug: I tried running attu image(https://hub.docker.com/layers/bitnami/attu/2.4.11/images/sha256-a3cc8b48d3cb5d3c8cf2a0a53a7b5f688b0cf526a4951e1db8a7f98aaae62937?context=explore) in our EKS environment. During the runtime it throws below error

pt/bitnami/node/lib/node_modules/corepack/dist/lib/corepack.cjs:22762 │ │ throw new Error( │ │ ^ │ │ │ │ Error: Error when performing the request to https://registry.npmjs.org/yarn/latest; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting │ │ at fetch (/opt/bitnami/node/lib/node_modules/corepack/dist/lib/corepack.cjs:22762:11) │ │ at process.processTicksAndRejections (node:internal/process/task_queues:95:5) │ │ at async fetchAsJson (/opt/bitnami/node/lib/node_modules/corepack/dist/lib/corepack.cjs:22776:20) │ │ ... 4 lines matching cause stack trace ... │ │ at async Object.runMain (/opt/bitnami/node/lib/node_modules/corepack/dist/lib/corepack.cjs:24232:5) { │ │ [cause]: TypeError: fetch failed │ │ at node:internal/deps/undici/undici:12618:11 │ │ at process.processTicksAndRejections (node:internal/process/task_queues:95:5) │ │ at async fetch (/opt/bitnami/node/lib/node_modules/corepack/dist/lib/corepack.cjs:22756:16) │ │ at async fetchAsJson (/opt/bitnami/node/lib/node_modules/corepack/dist/lib/corepack.cjs:22776:20) │ │ at async fetchLatestStableVersion (/opt/bitnami/node/lib/node_modules/corepack/dist/lib/corepack.cjs:22703:20) │ │ at async fetchLatestStableVersion2 (/opt/bitnami/node/lib/node_modules/corepack/dist/lib/corepack.cjs:22826:14) │ │ at async Engine.getDefaultVersion (/opt/bitnami/node/lib/node_modules/corepack/dist/lib/corepack.cjs:23433:23) │ │ at async Engine.executePackageManagerRequest (/opt/bitnami/node/lib/node_modules/corepack/dist/lib/corepack.cjs:23525:47) │ │ at async Object.runMain (/opt/bitnami/node/lib/node_modules/corepack/dist/lib/corepack.cjs:24232:5) { │ │ cause: [Error: 40AC17058B7F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:354: │ │ ] { │ │ library: 'SSL routines', │ │ reason: 'wrong version number', │ │ code: 'ERR_SSL_WRONG_VERSION_NUMBER' │ │ } │ │ } │ │ } │ │ │ │ Node.js v18.20.4

So in our EKS we block any public calls and here its trying to call npm registry which it shouldn't be calling.

Upon trying building attu docker image locally using attu Dockerfile, then uploaded this image to the AWS ecr, then used this image to deploy attu on EKS cluster -> this worked properly and is not doing any public call to npm registry.

Are we doing anything different while generating the attu Dockerimage uploaded to the dockerhub

Steps to reproduce:

1. Use attu image (https://hub.docker.com/layers/bitnami/attu/2.4.11/images/sha256-a3cc8b48d3cb5d3c8cf2a0a53a7b5f688b0cf526a4951e1db8a7f98aaae62937?context=explore) in EKS where public call is blocked.
2. During image run you will get above errors in attu pod logs.

Attu version: 2.4.7, 2.4.9,2.4.11 (We tried with these versions and error came in all the versions)

Attu version:

[shanghaikid]

You are using bitnami's attu, not ours.

https://hub.docker.com/r/zilliz/attu/tags can you try this? this one is build by the dockerfile that you used to build locally.

[aashishsingh2803]

Thanks, this helped Any specific reason on why does bitnami image not working, we use bitnami for most of the open source stuff like etcd, mongodb, fluentd etc.

[shanghaikid]

Thanks, this helped Any specific reason on why does bitnami image not working, we use bitnami for most of the open source stuff like etcd, mongodb, fluentd etc.

I have no idea, maybe they are using different base image which may be not compatible with your k8s system.