James Addison

Some possible clues from the `frontend` container: ```sh $ docker exec -it po_off-frontend-1 bash # head -n 5 /var/log/nginx/proxy-off-error.log 2025/06/05 13:30:04 [error] 36#36: *2 backend could not be resolved (3:...

Both the `po_off-frontend-1` (`nginx` webserver) and `po_off-backend-1` (ProductOpener `perl` web application) are configured as part of a Docker `po_off_default` network, according to their network settings. And the DNS names `frontend`...

An existing Slack thread for a similar-but-not-identical problem mentions that `docker ps` is a good first step to diagnose unavailable containers -- and it would seem to make sense that...

Removing the `./logs` directory from my local working clone of `openfoodfacts-server.git` has allowed the `backend:dev` container to start successfully as `po_off-backend-1`. That doesn't feel like the correct fix/resolution, but it...

> [ ... trimmed ... ] > One thing that might be interesting: Have you ever run the docker compose stack with a different user than the Makefile? The Makefile...

> If this was run as root using `sudo` first, and used with `make dev` later, then this difference in directory permissions might cause similar issues. Maybe I ran `make...

I think the `make`-run-inside-container theory is probably wrong. When I attempted that a few moments ago, it complained that `git` was not found: ```sh $ make build_taxonomies openfoodfacts-shared-services /bin/bash: line...

I'm going to close this because I think/hope it was an ephemeral issue encountered during testing. If similar errors occur again in future then this can be reopened.

Hi @Coryrichter94 - thanks for the bugreport. Please could you add some more details about what you expect to happen, and the results you're seeing - including any error messages?...

I'm relatively confident that upgrading to v15.0.0 should resolve this problem - but if not, let us know and we can reopen the bugreport.