-
Notifications
You must be signed in to change notification settings - Fork 210
Open
Labels
kind/bugSomething isn't workingSomething isn't working
Description
Expected Behavior
dpar init should provide actionable messages if it cannot proceed because a container is already running/a port is already in use
Actual Behavior
If a zipkin container is already running, the message is confusing
$ dapr init --container-runtime podman
⌛ Making the jump to hyperspace...
ℹ️ Container images will be pulled from Docker Hub
ℹ️ Installing runtime version 1.16.8
❌ Downloading binaries and setting up components...
❌ Error: something went wrong with the request: "proxy already running\n"
Steps to Reproduce the Problem
$ dapr uninstall --all --container-runtime podman
ℹ️ Removing Dapr from your machine...
ℹ️ Removing directory: /Users/xavier/.dapr/bin
ℹ️ Removing container: dapr_placement
ℹ️ Removing container: dapr_scheduler
ℹ️ Removing container: dapr_redis
ℹ️ Removing container: dapr_zipkin
ℹ️ Removing directory: /Users/xavier/.dapr
ℹ️ Removing volume if it exists: dapr_scheduler
✅ Dapr has been removed successfully
$ podman run --rm -d -p 9411:9411 --name zipkin openzipkin/zipkin
3cdb123fd7118ab7b2de2ed72fb4e206a5294e0971099ea9b8cf80a0aeed1869
$ dapr init --container-runtime podman
⌛ Making the jump to hyperspace...
ℹ️ Container images will be pulled from Docker Hub
ℹ️ Installing runtime version 1.16.8
❌ Downloading binaries and setting up components...
❌ Error: something went wrong with the request: "proxy already running\n"
My guess is that this is not podman or zipkin specific. In case it matters, MacOS Sequoia 15.7.3 with rootless podman 5.7.1
Release Note
RELEASE NOTE:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugSomething isn't workingSomething isn't working