question-mark
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.

Step 3/8 taking abnormally long time

See original GitHub issue

When deploying a Meteor 1.6 app using meteor-up 1.3.6, there is an abnormal amount of delay (5-10 minutes) on step 3 of 8:

Finished Extracting
Creating Dockerfile
Finished creating Dockerfile
Building image
Sending build context to Docker daemon  352.3MB
Step 1/8 : FROM abernix/meteord:node-8.4.0-binbuild
 ---> e5c01572b179
Step 2/8 : RUN mkdir /built_app
 ---> Using cache
 ---> c84525bca07f
Step 3/8 : COPY ./ /built_app

The app was originally deployed using the abernix/meteord:base image, but seems to have significantly slower deployment times using the abernix/meteord:node-8.4.0-binbuild image. I am not completely certain that the Docker image is the problem, it just seems strongly correlated.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:4
  • Comments:12 (8 by maintainers)

github_iconTop GitHub Comments

5reactions
zoderncommented, Jul 16, 2018

Mup 1.5 (#976) has a number of performance improvements. Two of them are related to Prepare Bundle:

  1. When building the image during Prepare Bundle, it set each environment variable in a separate build instruction in the docker file, which resulted in a new layer for each environment variable. It now sets all of the environment variables in one instruction. One of mup’s tests is 30 seconds faster due to this.
  2. The Start Meteor task would wait 15 seconds after creating the docker container before verifying deployment. Since Prepare Bundle helps the app to start faster, the task now only waits 3 seconds when it is enabled.
2reactions
zoderncommented, Jun 10, 2018

Version 1.4.5 is now available which adds the option app.docker.stopAppDuringPrepareBundle. When enabled the downtime is only the amount of time it takes to create the docker container and start the app, which can be as low as a few seconds.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Uterine Contraction: Cause for Concern When Patterns Are ...
A contraction that lasts longer than 90 seconds is called a “tetanic” contraction. Again, contractions lasting too long are abnormal and result ...
Read more >
ESENT Event 508 A Request to write to the file .... bytes ...
log" at offset 1306624 (0x000000000013f000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (21 seconds) to be serviced ...
Read more >
SQL Server Agent scheduled job taking abnormally long time to run ...
Usually the job should be finished in about 15 to 17 minutes (it works on pretty big data set having about 19 joins...
Read more >
My Pap Test Was Abnormal: Now What?
Once abnormal cells are identified, your doctor performs a biopsy, taking a small amount of tissue for testing. You'll feel a pinch, nothing...
Read more >
Abnormal long build time with podman build --layers #3136
${LOG} --> Using cache 65d09537d47e2e4fad48b7b43add8fed3f1cb779ad5a0b4825581d5b5b1e9ad8 STEP 37: USER app STEP 38: RUN mkdir -p ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found