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

[BUG] TAR_BAD_ARCHIVE : Unrecognized archive format #7988

Closed
2 tasks done
VishalMishraTss opened this issue Dec 17, 2024 · 6 comments
Closed
2 tasks done

[BUG] TAR_BAD_ARCHIVE : Unrecognized archive format #7988

VishalMishraTss opened this issue Dec 17, 2024 · 6 comments
Labels
Bug thing that needs fixing Duplicate duplicate of another, existing issue Registry specific to registry implementation

Comments

@VishalMishraTss
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

This issue exists in the latest npm version

  • I am using the latest npm

Current Behavior

while running RUN npm install pm2 -g in docker creation of my node app
I am getting:
npm error code TAR_BAD_ARCHIVE
npm error TAR_BAD_ARCHIVE: Unrecognized archive format

Dockerfile:
FROM node:18-slim

WORKDIR /usr/src/app

COPY package*.json ./

RUN npm i --only=production

COPY . .

RUN npm install pm2 -g

tried below also still same

RUN npm cache clean --force && npm install pm2 -g

EXPOSE 1337

CMD ["pm2-runtime", "dist/server.js"]

Expected Behavior

It should install pm2 properly in the docker container

Steps To Reproduce

  1. Docker base image tested on: node:18-slim, node:18,node:16,node:16-slim,node:alpine,node:latest,node:18-slim,node:18,node:22,node:20

2.Manually test the PM2 installation:
Run a temporary container for debugging:
docker run -it --rm node:18-slim bash
Inside the container, run:
npm cache clean --force && npm install -g pm2

error encountered:
npm error code TAR_BAD_ARCHIVE
npm error TAR_BAD_ARCHIVE: Unrecognized archive format

Environment

  • npm: 11.0.0
  • Node.js: v22.12.0
  • OS Name: Microsoft Windows [Version 10.0.22621.2861]
@VishalMishraTss VishalMishraTss added Bug thing that needs fixing Needs Triage needs review for next steps labels Dec 17, 2024
@atharva-unde
Copy link

Duplicate of #7986

@BRAVO68WEB
Copy link

Same, its again an India specific error. Ahh

@BRAVO68WEB
Copy link

Our AWS server in Mumbai are failing.
But, Singapore ones are up!

@Ganesh1991
Copy link

Facing same issue

70.30 npm error code TAR_BAD_ARCHIVE
70.30 npm error TAR_BAD_ARCHIVE: Unrecognized archive format
70.30 npm error A complete log of this run can be found in: /root/.npm/_logs/2024-12-17T13_05_42_763Z-debug-0.log

@Ganesh1991
Copy link

Issue with NPM site. you can track status from here https://status.npmjs.org/

@milaninfy
Copy link
Contributor

Closing as duplicate of #7986.

@milaninfy milaninfy closed this as not planned Won't fix, can't repro, duplicate, stale Dec 17, 2024
@milaninfy milaninfy added Registry specific to registry implementation Duplicate duplicate of another, existing issue and removed Needs Triage needs review for next steps labels Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Duplicate duplicate of another, existing issue Registry specific to registry implementation
Projects
None yet
Development

No branches or pull requests

5 participants