Issue starting demo with Podman

[dd4gg]

When I execute podman-compose, I hit the same issue:

$ podman pull ghcr.io/open-telemetry/demo:1.4.0-traceBasedTests
Trying to pull ghcr.io/open-telemetry/demo:1.4.0-traceBasedTests...
Error: initializing source docker://ghcr.io/open-telemetry/demo:1.4.0-traceBasedTests: reading manifest 1.4.0-traceBasedTests in ghcr.io/open-telemetry/demo: manifest unknown

Is this a valid container that is supposed to be in the ghcr.io ?

[svrnm]

@open-telemetry/demo-approvers please take a look.

@dd4gg you may consider raising this issue with the demo repository

[austinlparker]

Hi, I've transferred this issue to the demo repository.

[styblope]

I could replicate the issue and found the cause with multiple things playing out:

1. The image ghcr.io/open-telemetry/demo:1.4.0-traceBasedTests isn't indeed present in the repository because it isn't included in the GHA image build workflow.
2. The traceBasedTests service is associated with a profile in docker-compose.yml. Docker-compose services with assigned profiles aren't started unless one explicitly enables them using ``--profile` option. Therefore, the service should not be started using the normal demo startup command.
3. The reason podman-compose wants to pull the (nonexistent) image is because it doesn't yet implement profiles in the current v1.0.6 release; it will effectively start all containers declared in the compose file regardless the profile settings. The option is already merged in podman-compose upstream so hopefully due out soon.

If the various podman quirks get resolved, I think it would be worth opening up a discussion for qualifying podman as an inclusive build/run option next to docker.

[austinlparker]

Is this still an issue in 1.8?

[puckpuck]

It's been 11+ months since the PR to fix this in podman compose was merged, and still no release from their platform. Do we have any insight on if/when they will do a release?

The other way is to workaround the issue in podman compose and publish a traceBasedTests image as well as everything else we do. We already publish a frontendTests one, so I don't see why we can't add this one too.