Heroku docker spring boot image error 503 H14 Heroku docker spring boot image error 503 H14 docker docker

Heroku docker spring boot image error 503 H14


Finally I solved the question.The point is that the image in heroku must be named same as the process type, in this case web!

so there are two options. Build and pushing the image by using:

heroku container:push web -a petapp-authserver

or create the image locally and the tag it as registry.heroku.com/petapp-authserver/web

docker tag petapp-authserver registry.heroku.com/petapp-authserver/webdocker push registry.heroku.com/petapp-authserver/webThe push refers to repository [registry.heroku.com/petapp-authserver/web]eb03575d1edf: Preparingceaf9e1ebef5: Preparing9b9b7f3d56a0: Preparingf1b5933fe4b5: Preparingeb03575d1edf: Layer already exists9b9b7f3d56a0: Layer already existsf1b5933fe4b5: Layer already existsceaf9e1ebef5: Layer already existslatest: digest: sha256:4c0ae2bba092c07bbd89394216b0bf78f458ba3583e63c8d15e01f6b07d6933e size: 1159heroku container:release web -a petapp-authserverReleasing images web to petapp-authserver... done

Now my containers are perfectly running in docker!!

enter image description here

enter image description here

Thank you all


In your Procfile or your heroku.yml you have not specified a web worker.

2020-03-06T20:12:23.878827+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=petapp-authserver.herokuapp.com request_id=f83acdef-840a-4e2e-824c-183cfdc50273 fwd="79.147.107.220" dyno= connect= service= status=503 bytes= protocol=http

For containers you should use heroku.yml. Procfile might even be ignored.

https://devcenter.heroku.com/articles/build-docker-images-heroku-yml

Doing this will get rid of your current H14 errors.


Key point is the process type.

For example, when you deploy the jar and runs it, you can see at your logs:

remote: -----> Discovering process typesremote:        Procfile declares types -> web

But you don't see it when using release because you haven't specified a process type.Can you try to run the release command like this and see if it works?

heroku container:release web petapp-authserver -a petapp-authserver

web is the process type!