Skip to content

Main content

Docker Image Tag Colon Boundary Tool

Compute docker image tag colon boundary from explicit bounded inputs.

Loading tool…

Description

Split image and tag using the last colon after the last slash.

Package and container references combine names, selectors, conditions and platform metadata. A restricted lexical split can preserve these parts without validating registry identity, available targets, dependency graphs or runtime resolution.

Split image and tag using the last colon after the last slash.

When to use this tool

Use Docker Image Tag Colon Boundary when checking the stated package, Cargo or container-reference component.

How to use the tool and how it works

  1. Enter reference. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read image, tag, tagged. Inspect tagged before interpreting the associated values.

Split image and tag using the last colon after the last slash. Require nonempty whitespace-free reference without @; return tagged and tag, or an empty tag if no such colon.1

Input fieldMeaning and unitsAccepted input
referenceReferenceRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
imageImageRequired. Text; maximum UTF-16 length 8192.
tagTagRequired. Text; maximum UTF-16 length 8192.
taggedA colon exists after the final slash; a trailing colon can still yield an empty tag.Required. Boolean.
json
{
  "input": {
    "reference": "localhost:5000/app:latest"
  },
  "output": {
    "image": "localhost:5000/app",
    "tag": "latest",
    "tagged": true
  }
}

Limitations and assumptions

  • A trailing colon produces an empty tag with tagged = true; full reference grammar and registry lookup are omitted.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use the relevant package manager, runtime or registry against the actual project for complete resolution and validation.

References

  1. Calculation and input contract: development/docker-image-tag-colon-boundary — tool.io

Similar or alternative tools