Cli: heroku container:push returns 'Error: docker push exited with 1'

[MrSzymonello]

Do you want to request a feature or report a bug?

bug

What is the current behavior?

The steps to reproduce are:
heroku login
heroku container:login
heroku create returns damp-sands-66374
heroku container:push web --app damp-sands-66374

=== Building web (/root/iot-api-asp-net-core/src/Api/Dockerfile)
Sending build context to Docker daemon 32.53MB
Step 1/6 : FROM microsoft/aspnetcore
---> db030c19e94b
Step 2/6 : WORKDIR /dotnetapp
---> Using cache
---> 29be5363e1e2
Step 3/6 : COPY ./bin/Docker .
---> Using cache
---> 739553f29afa
Step 4/6 : ENV ASPNETCORE_URLS http://*:$PORT
---> Using cache
---> 0ceffd5c5e1e
Step 5/6 : ENV ASPNETCORE_ENVIRONMENT docker
---> Using cache
---> f9344ac55bc7
Step 6/6 : ENTRYPOINT dotnet Api.dll
---> Using cache
---> 5405910cc2cc
Successfully built 5405910cc2cc
Successfully tagged registry.heroku.com/damp-sands-66374/web:latest
=== Pushing web (/root/iot-api-asp-net-core/src/Api/Dockerfile)
The push refers to repository [registry.heroku.com/damp-sands-66374/web]
c7ef5aff4681: Pushed
ec1f562102cc: Pushed
94a7e5001357: Pushed
fea4f503ccf8: Pushed
3172a1c8308a: Pushed
264a7fdea008: Pushed
3b10514a95be: Pushed
unsupported
▸ Error: docker push exited with 1

heroku container:release web --app damp-sands-66374
▸ Expected response to be successful, got 404

What is the expected behavior?

Docker image is pushed to the heroku and then released and started.

heroku version: heroku/7.18.3 linux-x64 node-v10.12.0
Docker version: 18.06.1-ce, build e68fc7a
OS version: Ubuntu 18.04 LTS
firewall: /etc/init.d/firewalld status reports inactive state

[jdxcode]

This is an issue with the platform not the CLI. Would you mind submitting a support ticket instead?

[lucahuy]

@MrSzymonello: try changing ENTRYPOINT to CMD.

[jhalborg]

I just ran into this issue as well, did you get anything from support @MrSzymonello ?

[Soviut]

Just for posterity, I'm also running into this issue. I can't release a new app via containers.

[luqmanulkhair]

I am also facing the same issue.

[qmeeus]

Same here, I think this has to do with the use of entrypoint

[jhalborg]

To everyone running into this, the solution is to use CMD - it is mandatory in Heroku:

https://devcenter.heroku.com/articles/container-registry-and-runtime#dockerfile-commands-and-runtime

[aedifex]

+1 to running CMD ~ just fixed the issue for me.

[sneak]

praise google, this just saved me an asston of time