Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Prepare Bundle: FAILED

See original GitHub issue

I am trying to deploy a Meteor 1.6 site from Ubuntu 17.10 with mup 1.3.5 (since 1.3.6 has blocking bug). I have previously deployed the site with success, so am trying to update an existing deployment. When I run mup deploy, I get the following error (anonymized):

[example.com] x Prepare Bundle: FAILED

        -----------------------------------STDERR-----------------------------------
        '
        tar: Ignoring unknown extended header keyword 'SCHILY.dev'
        tar: Ignoring unknown extended header keyword 'SCHILY.ino'
        tar: Ignoring unknown extended header keyword 'SCHILY.nlink'
        tar: Ignoring unknown extended header keyword 'SCHILY.dev'
        tar: Ignoring unknown extended header keyword 'SCHILY.ino'
        tar: Ignoring unknown extended header keyword 'SCHILY.nlink'
        tar: Ignoring unknown extended header keyword 'SCHILY.dev'
        tar: Ignoring unknown extended header keyword 'SCHILY.ino'
        tar: Ignoring unknown extended header keyword 'SCHILY.nlink'
        tar: Ignoring unknown extended header keyword 'SCHILY.dev'
        tar: Ignoring unknown extended header keyword 'SCHILY.ino'
        tar: Ignoring unknown extended header keyword 'SCHILY.nlink'
        tar: Ignoring unknown extended header keyword 'SCHILY.dev'
        tar: Ignoring unknown extended header keyword 'SCHILY.ino'
        tar: Ignoring unknown extended header keyword 'SCHILY.nlink'
        Error response from daemon: Syntax error - can't find = in "ContainerName". Must be of the form: name=value
        -----------------------------------STDOUT-----------------------------------
        ifying Checksum
        9d9257716fcb: Download complete
        ad74af05f5a2: Verifying Checksum
        ad74af05f5a2: Download complete
        081b961ced66: Verifying Checksum
        081b961ced66: Download complete
        ae76c18a4a87: Verifying Checksum
        ae76c18a4a87: Download complete
        2223d111c785: Verifying Checksum
        2223d111c785: Download complete
        cac856543185: Verifying Checksum
        cac856543185: Download complete
        ad74af05f5a2: Pull complete
        e579369f8037: Pull complete
        a97dd394bc72: Verifying Checksum
        a97dd394bc72: Download complete
        037d29e186af: Verifying Checksum
        037d29e186af: Download complete
        037d29e186af: Pull complete
        9d9257716fcb: Pull complete
        ae76c18a4a87: Pull complete
        081b961ced66: Pull complete
        2223d111c785: Pull complete
        cac856543185: Pull complete
        a97dd394bc72: Pull complete
        Digest: sha256:3bf2aa0310a66416ae2a374faa18c59622a53ef09252f9e51c55cc855ad06a2a
        Status: Downloaded newer image for abernix/meteord:node-8.4.0-binbuild
        container_name
        Sending build context to Docker daemon  352.3MB
        container_name

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:9

Top GitHub Comments

1reaction

elie222commented, Apr 13, 2018

So I think it has to do with the device running out of space.

Check how much space you have left:

df -h

To free up space from docker run:

docker system prune

1reaction

elie222commented, Nov 27, 2017

I’m getting this error when attempting again:

Started TaskList: Pushing Meteor App
[34.xx] - Pushing Meteor App Bundle to the Server
[34.xx] - Pushing Meteor App Bundle to the Server: SUCCESS
[34.xx] - Prepare Bundle
[34.xx] x Prepare Bundle: FAILED

        -----------------------------------STDERR-----------------------------------
        pt/bin: implausibly old time stamp 1970-01-01 00:00:00
        tar: bundle/programs/server/npm/node_modules/meteor/iron_router/node_modules/grunt/node_modules/nopt/examples: implausibly old time stamp 1970-01-01 00:00:00
        tar: bundle/programs/server/npm/node_modules/meteor/iron_router/node_modules/grunt/node_modules/nopt/lib: implausibly old time stamp 1970-01-01 00:00:00
        tar: bundle/programs/server/npm/node_modules/meteor/iron_router/node_modules/grunt/node_modules/nopt/node_modules: implausibly old time stamp 1970-01-01 00:00:00
        tar: bundle/programs/server/npm/node_modules/meteor/iron_router/node_modules/grunt/node_modules/rimraf/test: implausibly old time stamp 1970-01-01 00:00:00
        tar: bundle/programs/server/npm/node_modules/meteor/iron_router/node_modules/grunt/node_modules/underscore.string/dist: implausibly old time stamp 1970-01-01 00:00:00
        tar: bundle/programs/server/npm/node_modules/meteor/iron_router/node_modules/grunt/node_modules/underscore.string/lib: implausibly old time stamp 197
        -----------------------------------STDOUT-----------------------------------
        node-8.4.0-base: Pulling from abernix/meteord
        Digest: sha256:04f44cf999da383d11de77027ced8b70818222c9890a405ce10803af3ee5a642
        Status: Image is up to date for abernix/meteord:node-8.4.0-base
        draftapp
        ----------------------------------------------------------------------------

Top Results From Across the Web

Mup fails at prepare bundle · Issue #734 · zodern/meteor-up

Failed at the meteor-dev-bundle@0.0.0 install script 'node npm-rebuild.js'. npm ERR! Make sure you have the latest version of node.js and npm ...

meteor up Prepare Bundle: FAILED - Stack Overflow

Any help. I have been on this deployment issue for more than 4 days. I have to upgrade the server to KVM today....

Failed to register bundle identifi… | Apple Developer Forums

I tried to manually add the Bundle ID on the developer portal and I get this error: An App ID with Identifier ''...

Create an application source bundle - AWS Elastic Beanstalk

When you use the AWS Elastic Beanstalk console to deploy a new application or an application version, you'll need to upload a source...

Upgrade a Cisco ISE Deployment from the CLI

The application upgrade prepare command downloads the upgrade bundle and extracts it locally. This command copies the upgrade bundle from the remote ...