[Bug] Failure to start containers using podman compose

[Prathyush-KKK]

Describe the bug When attempting to start the project using Podman Compose, several services fail to build because the specified Dockerfile.gh files cannot be found in their respective build contexts.

To Reproduce Steps to reproduce the behavior:

1. Clone the repository on Windows.

podman compose -f hosting/docker-compose/oss/docker-compose.gh.yml --env-file hosting/docker-compose/oss/.env.oss.gh --profile with-web --profile with-traefik up -d

2. Observe build errors for api, chat, and completion services.

Expected behavior Podman Compose should find and build all required Dockerfiles (oss/docker/Dockerfile.gh) for each service.

Desktop:

• OS: Windows 11
• Podman: podman-compose (installed via Python, running on WSL2 backend)
• Version: Podman 5.6.0 (example, adjust with your actual version)

---

[dosubot[bot]]

Hi @Prathyush-KKK! I'm Dosu and I’m helping the agenta team.

The Dockerfile.gh files for api, chat, and completion do exist in the repository and are correctly referenced in the docker-compose.gh.yml file, as long as you run the compose command from the hosting/docker-compose/oss directory. On Windows/WSL2, build errors like this are often caused by path translation issues, case sensitivity mismatches, or symlink handling between Windows and Linux filesystems.

Make sure you’re running the command from hosting/docker-compose/oss, and double-check that the file and directory names match exactly (including case). If you’re still seeing errors, try running the same command inside your WSL2 shell rather than from a Windows terminal, as Podman Compose may interpret paths differently depending on the environment.

Also, note that the 'gh' Dockerfiles are not recommended for deployment—they have incomplete Traefik configuration and may not expose the necessary ports. For a smoother deployment, consider switching to the 'dev' Dockerfile instead, which is the recommended option for Agenta deployments (source).

If you need to compare behavior, you can try using Docker Compose as well, since it sometimes handles paths more predictably on Windows/WSL2.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[mmabrouk]

Hello @Prathyush-KKK,

Thanks for opening this issue, couple of questions:

• Do you see these errors when using docker compose or are they limited to podman
• Can you please share the logs
• The command that you shared (at least in docker compose) does not build the images, just pull them for the repo and run them. It's strange that you got build errors in this case