images::stat

Tag 16: a client names an image from its listing; the server sends exactly one response carrying the image as the listing reports it and the Containerfile it was built from, or an error, and the scope finishes.

A client opens the scope with a request whose payload is the tag byte 16 followed by the name of an image. The server sends exactly one response, which is the image examined, the word that the server keeps no client image, or an error. The response finish follows the response, and no frame follows the finish.

• The request. The request carries the name of one image. Request states its form.
• The image named. The client names an image by the name its images::list listing gave it. The server resolves the name against the identity under which the connection was authorized, as Authorization provides. A name that is not in the client’s listing is answered with an error. A client cannot name another client’s image.
• The answer. The answer carries the four fields the listing reports for the image, and one more: the Containerfile it was built from. Response states its form.
• The error. An error states that the image was not examined, and that nothing was determined about it. An image absent from the client’s listing is answered with an error.
• No image store. A server that holds out no images_store capability keeps no client image and answers every request of this endpoint with exactly one response, the byte 1 alone, and the response finish, before anything is looked up. Every other requirement of this page holds for a server that holds the capability out.