Pushing a non existent tag doesn't raise an exception

I get this error in the error output but no exception is raised:

{"status":"The push refers to repository [485757098324.dkr.ecr.us-east-1.amazonaws.com/ssh_proxy]"}
{"errorDetail":{"message":"An image does not exist locally with the tag: 485757098324.dkr.ecr.us-east-1.amazonaws.com/ssh_proxy"},"error":"An image does not exist locally with the tag: 485757098324.dkr.ecr.us-east-1.amazonaws.com/ssh_proxy"}

Unlike related issue #1772 there's really no excuse here, since this error can be detected even if trying to push to a black box, while #1772 requires understanding the output of a repo server.

Also worth mentioning that the docker push command WILL return an error code in this case. So actually the docker push command gives MORE info than the SDK function. Since the docker push command gives output + error code. While the SDK function only gives output :(

(Not saying the function needs to BC break and return two values, just that it needs to raise exceptions when appropriate)

Start by locating the SDK function used for docker push and tracing how its streamed error output is handled. Reproduce the case with a nonexistent local tag and compare the SDK result with docker push's nonzero exit behavior. Done means the SDK raises an exception for this client-detectable error while preserving the existing output behavior.