gnodet commented on PR #22287: URL: https://github.com/apache/camel/pull/22287#issuecomment-4142835420
@Croway Good question! I looked into this — `camel infra run` manages services via PID files in `~/.camel/` (e.g., `infra-redis-<PID>.json`), not by container name. `camel infra stop`, `camel infra ps`, etc. all use this PID-based tracking. So the PID+counter suffix in the container name doesn't break any lifecycle management. That said, I understand the UX concern: if someone runs `docker ps`, seeing `camel-kafka` is nicer than `camel-kafka-12345-1`. Do you still think we should avoid the suffix specifically for the `camel infra run` use case? We could potentially use the `camel.infra.fixedPort` property as a signal — when it's `true` (set by JBang), skip the PID+counter and use the clean name, since in that mode only one instance runs at a time. Would that be doable? _Claude Code on behalf of Guillaume Nodet_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
