我正在使用Kadira的Meteor-Up (Mup)来部署我的meteor应用程序。我已经从Mupx更新了Mup,这可能是导致问题的原因。
这是配置文件
module.exports = {
servers: {
one: { /* ssh auth details here */ }
}
},
meteor: {
name: 'soundcraft',
path: '.',
docker: {
image: 'kadirahq/meteord',
},
servers: {
one: {}
},
buildOptions: {
serverOnly: true,
debug: true,
cleanAfterBuild: true,
},
"env": {
"ROOT_URL": "http://139.232.218.147",
"MONGO_URL": "mongodb://localhost:27017/soundcraft"
},
deployCheckWaitTime: 60
},
mongo: {
oplog: true,
port: 27017,
servers: {
one: {},
},
},
};mup setup运行正常,但当我使用DEBUG=* mup deploy命令时,会产生以下错误:
mup:module:default exec => mup deploy +0ms
mup:module:meteor exec => mup meteor deploy +2ms
mup:module:meteor exec => mup meteor push +2ms
Building App Bundle Locally
Started TaskList: Pushing Meteor
[139.232.218.147] - Pushing Meteor App Bundle to The Server
nodemiral:sess:139.162.208.147 copy file - src: /tmp/62ab2c11-1477-4248-a409-392ca66940f0/bundle.tar.gz, dest: /opt/soundcraft/tmp/bundle.tar.gz, vars: undefined +0ms
[139.232.218.147] - Pushing Meteor App Bundle to The Server: SUCCESS
[139.232.218.147] - Pushing the Startup Script
nodemiral:sess:139.232.218.147 copy file - src: /Users/imac/.nvm/versions/node/v4.5.0/lib/node_modules/mup/lib/modules/meteor/assets/templates/start.sh, dest: /opt/soundcraft/config/start.sh, vars: {"appName":"soundcraft","useLocalMongo":1,"port":80,"logConfig":{"opts":{"max-size":"100m","max-file":10}},"docker":{"image":"kadirahq/meteord"}} +7s
[139.232.218.147] - Pushing the Startup Script: SUCCESS
mup:module:meteor exec => mup meteor envconfig +3m
Started TaskList: Configuring Meteor Environment Variables
[139.232.218.147] - Sending Environment Variables
nodemiral:sess:139.232.218.147 copy file - src: /Users/imac/.nvm/versions/node/v4.5.0/lib/node_modules/mup/lib/modules/meteor/assets/templates/env.list, dest: /opt/soundcraft/config/env.list, vars: {"env":{"ROOT_URL":"http://139.232.218.147","MONGO_URL":"mongodb://localhost:27017/soundcraft","METEOR_SETTINGS":"{\"public\":{}}"},"appName":"soundcraft"} +433ms
[139.232.218.147] - Sending Environment Variables: SUCCESS
mup:module:meteor exec => mup meteor start +456ms
Started TaskList: Start Meteor
[139.232.218.147] - Start Meteor
[139.232.218.147] x Start Meteor: FAILED
-----------------------------------STDERR-----------------------------------
Error response from daemon: No such container: soundcraft-frontend
docker: Error response from daemon: driver failed programming external connectivity on endpoint soundcraft (22e4ffc6ecf94ffc1d35ebaf0e3f3364c92e3079439ca2e0138a5951b068f481): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use.
-----------------------------------STDOUT-----------------------------------
soundcraft
Using default tag: latest
latest: Pulling from kadirahq/meteord
Digest: sha256:7ec54d5fafc11acbcc82f3e555fddce8e4742ddeda05a64997f2a10e3c04137e
Status: Image is up to date for kadirahq/meteord:latest
6e357baf5700be59d64973ff9653ca2eb80eaa2e52145411ce6d5d42d0a4d109
----------------------------------------------------------------------------在做了一些搜索之后,我发现了一些关于让docker使用不同的端口的东西,所以我试着在配置中添加额外的一行来做到这一点,但我不确定具体是怎么做的。
发布于 2016-11-06 18:08:45
您可以在env中添加端口,如下所示:
环境:{ PORT: 8010,ROOT_URL:"http://139.232.218.147",MONGO_URL:"mongodb://localhost:27017/soundcraft“},
干杯,科索纳
发布于 2016-11-07 06:22:08
我找到了原因,我想和大家分享。
使用mup setup确保在mup.js中,每个块中的最后一行以空格结尾,而不是,。如果最后一个块以结束,您将看到进程卡住并得到超时错误。示例:下面是正确的。调试:{ serverOnly: true,buildOptions: true,cleanAfterBuild: true },
下面的代码将生成错误调试buildOptions:{ serverOnly: true,:true,cleanAfterBuild: true,},
使用mup deploy确保在settings.json中每个块中的最后一行以空格结尾,而不是,。如果最后一个块以结束,您将看到进程卡住并得到超时错误。示例:下面是正确的。"oAuth":{
“推特”:{
"consumerKey":"xxx",
"secret":"xxxx","access_token_key":"xxx","access_token_secret":"xxx“
},
"facebook":{
"appId":"xxx",
"secret":"xxxx“
}}
下面将生成error timeout "oAuth":{
“推特”:{
"consumerKey":"xxx",
"secret":"xxxx","access_token_key":"xxx","access_token_secret":"xxx“
},
"facebook":{
"appId":"xxx",
"secret":"xxxx“
},}
希望这能有所帮助!
干杯,科索纳
https://stackoverflow.com/questions/39446956
复制相似问题