[BUG] - The process type web was not updated, because it is already running the specified docker image/

[dahal]

What is the current behavior?

The process type web was not updated even when i have a lot of changes on my app. Assets compiled but it failed to release the on web, worker was fine.

What is the expected behavior?

1. Why did this happen? Looking at the CHANGELOG, nothing mentions about this bug/fix. So i dont think the issue will be resolved after suggested update.

[dahal]

Also, we have been deploying for months on container, this is the first time it has happened to us, so just wanted to make sure why this happened so we can avoid this for happening again.

[olvina]

@dahal how did you solve this?

[dahal]

@olvina re-deployed app, that released the app and worker both just fine (on 2nd deploy), but this should not have happen in the first place or the build/release should have failed. A lot of our workers broke because of the updated files, methods on app/workers.

[Junkern]

I also encountered this bug. My last deploy was at the end of November and now I wanted to deploy a new version of my app, but: The process type web was not updated, because it is already running the specified docker image.

The previous times the deployment with the exact same commands worked perfectly

My application is running in a docker container. I only have a web process type. Version of heroku-cli is 7.47.6

Any ideas @heroku-cli ?

If it is of any use, here is my deploy script:

docker build -t libreoffice-server .
docker tag libreoffice-server registry.heroku.com/xxxx-my-app/web
docker push registry.heroku.com/xxxx-my-app/web
heroku container:release web -a xxxx-my-app

[mridpin]

Happened to me as well, just as you describe it. It seems it won't ovewrite an already existing image, it just returns that error. However I can overwrite images from the API

[jmjuanico]

anybody has found a workaround for this?

[MikeNatty]

I haven't found reliable workaround. It's definitely not a new issue though. Very frustrating... especially when under time pressure.

[q00Dree]

I also encountered this bug. My last deploy was at the end of November and now I wanted to deploy a new version of my app, but: The process type web was not updated, because it is already running the specified docker image.

The previous times the deployment with the exact same commands worked perfectly

My application is running in a docker container. I only have a web process type. Version of heroku-cli is 7.47.6

Any ideas @heroku-cli ?

If it is of any use, here is my deploy script:

docker build -t libreoffice-server .
docker tag libreoffice-server registry.heroku.com/xxxx-my-app/web
docker push registry.heroku.com/xxxx-my-app/web
heroku container:release web -a xxxx-my-app

Hello, did you find the solution? I do deploy like you

[MikeNatty]

This bug just reared it's ugly head again :( Been trying to deploy since last night. Very frustrating. Any advice from the Heroku team?

[0xradical]

If you're not logged in on heroku container (you can use heroku container:login), the image will fail to push and whenever you try to release it will correctly output this message.

[Junkern]

@thiagobrandam thanks for the tip! I now can deploy. For others reading this: I only deploy once every 3-4 months. Of course I am logged out of the heroku cli, since the last login was a long time ago. In addition to a heroku login I also have to do a heroku container:login. Then it works perfectly :)