[editorial] Invalid URLs from Docker docs

[vitorvasc]

The latest reference cache update in the OTel.io repo (see open-telemetry/opentelemetry.io#8480) surfaced a few 404s coming from Docker documentation URLs:

docs/specs/semconv/registry/entities/container/index.html
  fresh --- docs/specs/semconv/registry/entities/container/index.html --> https://docs.docker.com/reference/api/engine/version/v1.43/#tag/Image/operation/ImageInspect
  hitting --- docs/specs/semconv/registry/entities/container/index.html --> https://docs.docker.com/reference/api/engine/version/v1.43/#tag/Image/operation/ImageInspect
  Non-OK status: 404 --- docs/specs/semconv/registry/entities/container/index.html --> https://docs.docker.com/reference/api/engine/version/v1.43/#tag/Image/operation/ImageInspect
  fresh --- docs/specs/semconv/registry/entities/container/index.html --> https://docs.docker.com/reference/api/engine/version/v1.43/#tag/Container/operation/ContainerInspect
  hitting --- docs/specs/semconv/registry/entities/container/index.html --> https://docs.docker.com/reference/api/engine/version/v1.43/#tag/Container/operation/ContainerInspect
  Non-OK status: 404 --- docs/specs/semconv/registry/entities/container/index.html --> https://docs.docker.com/reference/api/engine/version/v1.43/#tag/Container/operation/ContainerInspect
  fresh --- docs/specs/semconv/registry/entities/container/index.html --> https://docs.docker.com/reference/api/engine/version/v1.43/#tag/Image/operation/ImageInspect
  hitting --- docs/specs/semconv/registry/entities/container/index.html --> https://docs.docker.com/reference/api/engine/version/v1.43/#tag/Image/operation/ImageInspect
  Non-OK status: 404 --- docs/specs/semconv/registry/entities/container/index.html --> https://docs.docker.com/reference/api/engine/version/v1.43/#tag/Image/operation/ImageInspect

These links appear in the registry section, under both Container Attributes and Container Entities entities pages.

Do we know what the correct replacement URLs should be?

[thompson-tomo]

I have attempted to fix it via #3093 but it was auto-closed. ☹️ is there a way on docs side that the links could be updated without triggering a full release of semconv? See my pr for updated links

[vitorvasc]

Oh, thanks for sharing this @thompson-tomo!

is there a way on docs side that the links could be updated without triggering a full release of semconv?

That is a great question — I haven't run into this particular scenario before.

Looping in @chalin for some expertise here. 🙌🏼

[lmolkova]

closed via #3093, thanks @thompson-tomo and @vitorvasc

[vitorvasc]

Thank you @lmolkova!