Closed ddaydd closed 4 months ago
Same boat here!
x Prepare Bundle: FAILED
------------------------------------STDERR------------------------------------
------------------------------------STDOUT------------------------------------
Updating base image
root: Pulling from zodern/meteor
Digest: sha256:0a2d5104d177d06131b39d7321e2edd8ecd301d438c188e55d9ac173c0ab10fb
Status: Image is up to date for zodern/meteor:root
docker.io/zodern/meteor:root
Preparing for docker build
Creating Dockerfile
Finished creating Dockerfile
Building image
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
BuildKit is currently disabled; enable it by removing the DOCKER_BUILDKIT=0
environment-variable.
Sending build context to Docker daemon 607.3MB
Step 1/13 : FROM zodern/meteor:root
# Executing 6 build triggers
---> Using cache
---> Using cache
---> Using cache
---> Using cache
---> Using cache
---> Using cache
---> 6f03e4357401
Step 2/13 : RUN mkdir /built_app || true
---> Using cache
---> 818d85bc358b
Step 3/13 : ARG ROOT_URL
---> Using cache
---> 92624914c683
Step 4/13 : ARG MONGO_URL
---> Using cache
---> f4d064c09d41
Step 5/13 : ARG MAIL_URL
---> Using cache
---> 7ceef893e1af
Step 6/13 : ARG VIRTUAL_HOST
---> Using cache
---> 7ca8ce24e08d
Step 7/13 : ARG HTTPS_METHOD
---> Using cache
---> 554f6f297266
Step 8/13 : ARG LETSENCRYPT_HOST
---> Using cache
---> 4773800f9e43
Step 9/13 : ARG LETSENCRYPT_EMAIL
---> Using cache
---> 455f56d4bafa
Step 10/13 : ARG VIRTUAL_PORT
---> Using cache
---> 1109ba950e0a
Step 11/13 : ARG HTTP_FORWARDED_COUNT
---> Using cache
---> c7d7ca72c2b9
Step 12/13 : COPY ./ /built_app
---> 49bc44e5adae
Step 13/13 : RUN cd /built_app/programs/server && npm install --unsafe-perm
---> Running in 97d38c2019c3
npm WARN deprecated node-pre-gyp@0.15.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm ERR! code E503
npm ERR! 503 Service Unavailable - GET https://codeload.github.com/meteor/node-source-map-support/legacy.tar.gz/
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2023-09-05T04_15_08_313Z-debug.log
The command '/bin/sh -c cd /built_app/programs/server && npm install --unsafe-perm' returned a non-zero code: 1
real 7m57.154s
user 0m4.713s
sys 0m5.554s
Sorry, I think I used the wrong image docker From Meteor guide
In order to correctly run projects in Meteor 2.13 with Docker, you will need to update your Dockerfile to use our Docker image that contains Nodejs v14.21.4.
but now I have
Container has no IP Address, likely from the app crashing
x Verifying Deployment: FAILED
------------------------------------STDERR------------------------------------ curl: (7) Failed to connect to 172.17.0.7 port 3000 after 0 ms: Couldn't connect to server curl: (7) Failed to connect to 172.17.0.7 port 3000 after 0 ms: Couldn't connect to server Container spent too much time restarting. => Logs: => Redeploying previous version of the app ------------------------------------STDOUT------------------------------------ CONTAINER IP EMPTY IP: Container has no IP Address, likely from the app crashing. CONTAINER IP EMPTY
and mup logs
[xxx.xxx.xxx.xxx]=> Setting node version [xxx.xxx.xxx.xxx]NODE_VERSION=14.21.3 [xxx.xxx.xxx.xxx]v14.21.3 is already installed. [xxx.xxx.xxx.xxx]Now using node v14.21.3 (npm v6.14.18) [xxx.xxx.xxx.xxx]default -> 14.21.3 (-> v14.21.3 *) [xxx.xxx.xxx.xxx]=> Starting meteor app on port 3000
It's possible that there can be changes made to the Meteor-Docker container to help make 2.13 work, but for now I think it's best to stick to 2.12.
https://github.com/zodern/meteor-docker/issues/32#issuecomment-1677723246
FWIW, I cleared out my node_modules
folder and re-ran meteor npm install
. That did the trick and pushed it through.
(Also, I'm still on 2.12)
Hi there, Check this issue for more infos. HTH
Hello everyone,
I can no longer deploy as soon as I upgrade to version METEOR@2.13, it's only me???
Thanks for your help