We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using main latest 8e8674f
Running on Ubuntu 22.04 LTS, x86_64
payment-service won't start with docker-compose.
$ docker compose up [+] Running 14/0 ⠿ Container jaeger Running 0.0s ⠿ Container grafana Running 0.0s ⠿ Container postgres Running 0.0s ⠿ Container otel-col Running 0.0s ⠿ Container product-catalog-service Running 0.0s ⠿ Container email-service Running 0.0s ⠿ Container currency-service Created 0.0s ⠿ Container recommendation-service Running 0.0s ⠿ Container prometheus Running 0.0s ⠿ Container feature-flag-service Running 0.0s ⠿ Container redis-cart Running 0.0s ⠿ Container ad-service Running 0.0s ⠿ Container cart-service Running 0.0s ⠿ Container shipping-service Running 0.0s Attaching to ad-service, cart-service, checkout-service, currency-service, email-service, feature-flag-service, frontend, grafana, jaeger, load-generator, otel-col, payment-service, postgres, product-catalog-service, prometheus, recommendation-service, redis-cart, shipping-service Error response from daemon: driver failed programming external connectivity on endpoint payment-service (fa763d449aa0b5b2ed3e1af872efb67e8841179f5eae2cb59cc25b20b094a8f5): Error starting userland proxy: listen tcp4 0.0.0.0:50051: bind: address already in use
Possibly related to the recent port change #248
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Bug Report
Which version of the demo you are using?
Using main latest
8e8674f
Running on Ubuntu 22.04 LTS, x86_64
Symptom
payment-service won't start with docker-compose.
Additional Context
Possibly related to the recent port change #248
The text was updated successfully, but these errors were encountered: