You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes @Paloma-Sanchez seems to have issues where she runs a Docker image but Dokcer uses an outdated version and bugs aren't fixed as expected. To help detecting this, I suggest we add a route which returns informations about the api version.
We should return the tag, but also the date at which the image was built, which is far easier to reason with.
Also, since we won't have the opportunity to return the current tag for edge and local builds, returning the build date will make total sense.
On the version information route, we could return an object like this:
Sometimes @Paloma-Sanchez seems to have issues where she runs a Docker image but Dokcer uses an outdated version and bugs aren't fixed as expected. To help detecting this, I suggest we add a route which returns informations about the api version.
We should return the tag, but also the date at which the image was built, which is far easier to reason with.
Also, since we won't have the opportunity to return the current tag for edge and local builds, returning the build date will make total sense.
On the version information route, we could return an object like this:
This way, we'd support adding more keys in the future if needed.
For local builds, it could look like:
(We might want to add commit information if there are no unstaged changes.)
Finally, for edge builds it'd look like this:
The text was updated successfully, but these errors were encountered: