It turned out to be very difficult executing a command using az (the revision error was not due to me trying to add a new revision, it appeared to be an old ghost from a previous time when multiple revisions were enabled) or trying any variants of the command directly. As a last resort I toggled between single and multiple revision mode (using the portal) to get rid of this mysterious old artefact and then the exactly same container update worked successfully.