Docker compose restarting service with docker.io/library/ container

Describe the Bug

docker_compose will not register a service as running if one of the containers uses an image in the form docker.io/library/<name>. This seems to be an old format but it is still valid and used (eg. by authentik).

Expected Behavior

The provider should handle prefixes like this and ignore them when looking for running containers. The running container will show <name>:<version> rather than docker.io/library/<name>:<version>.

Steps to Reproduce

Steps to reproduce the behavior:

1. Deploy authentik with the docker_compose resource
   1. Something like

docker_compose { 'authentik':
    ensure => present,
    compose_files => ['/my.compose.yaml']
}

3. Run puppet several times, each time it will report the service is not running and restart it.

Environment

• Version 7.0.0
• Platform Ubuntu 22.04

Additional Context

I followed the authentik docs for setup and then moved the .env and docker-compose.yaml files to puppet

Start with the docker_compose resource's handling of image names and compare the configured image form with the name reported for running containers. Reproduce the authentik-style compose setup on Ubuntu 22.04, then verify repeated Puppet runs recognize the service as running instead of restarting it.