我可以将Elgg docker映像部署到Heroku吗?

时间:2019-10-06 09:44:41

标签: docker heroku elgg

我正在设置Heroku应用程序以通过Docker图像容器使用Elgg CMS创建社交网络吗?我已经在我的Heroku应用程序中部署了linuxconfig / elgg映像,但是似乎有一个错误,我的应用程序无法启动。

这是我的命令。

docker tag linuxconfig/elgg registry.heroku.com/mtb-elgg/web
docker push registry.heroku.com/mtb-elgg/web
heroku container:release web --app mtb-elgg
heroku open --app mtb-elgg

这是一些日志

2019-10-06T09:22:30.518758+00:00 heroku[web.1]: Starting process with command `supervisord`
2019-10-06T09:22:33.196097+00:00 app[web.1]: 2019-10-06 09:22:33,195 WARN Included extra file "/etc/supervisor/conf.d/supervisor-lamp.conf" during parsing
2019-10-06T09:22:33.221857+00:00 app[web.1]: 2019-10-06 09:22:33,221 INFO RPC interface 'supervisor' initialized
2019-10-06T09:22:33.223149+00:00 app[web.1]: 2019-10-06 09:22:33,223 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2019-10-06T09:22:33.223715+00:00 app[web.1]: 2019-10-06 09:22:33,223 INFO supervisord started with pid 4
2019-10-06T09:22:34.230848+00:00 app[web.1]: 2019-10-06 09:22:34,230 INFO spawned: 'mysqld' with pid 7
2019-10-06T09:22:34.234061+00:00 app[web.1]: 2019-10-06 09:22:34,233 INFO spawned: 'apache2' with pid 8
2019-10-06T09:22:34.422769+00:00 app[web.1]: 2019-10-06 09:22:34,422 INFO exited: apache2 (exit status 1; not expected)
2019-10-06T09:22:35.857627+00:00 app[web.1]: 2019-10-06 09:22:35,857 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-06T09:22:35.861032+00:00 app[web.1]: 2019-10-06 09:22:35,860 INFO spawned: 'apache2' with pid 360
2019-10-06T09:22:36.057382+00:00 app[web.1]: 2019-10-06 09:22:36,057 INFO exited: apache2 (exit status 1; not expected)
2019-10-06T09:22:38.063821+00:00 app[web.1]: 2019-10-06 09:22:38,063 INFO spawned: 'apache2' with pid 362
2019-10-06T09:22:38.176301+00:00 app[web.1]: 2019-10-06 09:22:38,176 INFO exited: apache2 (exit status 1; not expected)
2019-10-06T09:22:41.187058+00:00 app[web.1]: 2019-10-06 09:22:41,186 INFO spawned: 'apache2' with pid 363
2019-10-06T09:22:41.326787+00:00 app[web.1]: 2019-10-06 09:22:41,326 INFO exited: apache2 (exit status 1; not expected)
2019-10-06T09:22:41.699528+00:00 heroku[web.1]: source=web.1 dyno=heroku.148693767.f817a3ac-fa5f-4b5a-a680-c76da2e68512 sample#memory_total=72.07MB sample#memory_rss=43.75MB sample#memory_cache=28.32MB sample#memory_swap=0.00MB sample#memory_pgpgin=33269pages sample#memory_pgpgout=14819pages sample#memory_quota=512.00MB
2019-10-06T09:22:42.331771+00:00 app[web.1]: 2019-10-06 09:22:42,331 INFO gave up: apache2 entered FATAL state, too many start retries too quickly
2019-10-06T09:23:03.871603+00:00 heroku[web.1]: source=web.1 dyno=heroku.148693767.f817a3ac-fa5f-4b5a-a680-c76da2e68512 sample#memory_total=72.07MB sample#memory_rss=43.75MB sample#memory_cache=28.32MB sample#memory_swap=0.00MB sample#memory_pgpgin=33269pages sample#memory_pgpgout=14819pages sample#memory_quota=512.00MB
2019-10-06T09:23:25.695473+00:00 heroku[web.1]: source=web.1 dyno=heroku.148693767.f817a3ac-fa5f-4b5a-a680-c76da2e68512 sample#load_avg_1m=0.00
2019-10-06T09:23:25.734812+00:00 heroku[web.1]: source=web.1 dyno=heroku.148693767.f817a3ac-fa5f-4b5a-a680-c76da2e68512 sample#memory_total=72.07MB sample#memory_rss=43.75MB sample#memory_cache=28.32MB sample#memory_swap=0.00MB sample#memory_pgpgin=33269pages sample#memory_pgpgout=14819pages sample#memory_quota=512.00MB
2019-10-06T09:23:30.846983+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2019-10-06T09:23:30.88126+00:00 heroku[web.1]: Stopping process with SIGKILL
2019-10-06T09:23:31.06174+00:00 heroku[web.1]: Process exited with status 137
2019-10-06T09:23:31.116397+00:00 heroku[web.1]: State changed from starting to crashed
2019-10-06T09:23:31.119714+00:00 heroku[web.1]: State changed from crashed to starting
2019-10-06T09:23:42.164767+00:00 heroku[web.1]: Starting process with command `supervisord`
2019-10-06T09:23:44.087869+00:00 app[web.1]: 2019-10-06 09:23:44,087 WARN Included extra file "/etc/supervisor/conf.d/supervisor-lamp.conf" during parsing
2019-10-06T09:23:44.09843+00:00 app[web.1]: 2019-10-06 09:23:44,098 INFO RPC interface 'supervisor' initialized
2019-10-06T09:23:44.098532+00:00 app[web.1]: 2019-10-06 09:23:44,098 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2019-10-06T09:23:44.098711+00:00 app[web.1]: 2019-10-06 09:23:44,098 INFO supervisord started with pid 4

0 个答案:

没有答案