Pravega docker image unusable on Windows
See original GitHub issueDescribe the bug When using the Pravega docker image on Windows, Pravega client cannot connect to segment store.
To Reproduce Steps to reproduce the behavior:
- Run docker image:
docker run -it -p 9090:9090 -p 12345:12345 pravega/pravega:latest standalone
- Run pravega-cli from outside of docker:
./bin/pravega-cli
- Notice you can create scopes and streams, but you can cannot append to a stream
Additional information Docker for Windows forces the container to run on an internal Hyper-V subnet, causing Pravega to hand out invalid connection settings for the segment store. Pravega needs to be able to distinguish between internal and external connection settings.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
pravega/pravega - Docker Image - Docker Hub
Pravega - Streaming as a new software defined storage primitive. ... you can run a standalone Pravega in a docker container, the command...
Read more >Running Locally - Exploring Pravega
The below command will download and run Pravega from the container image on docker hub. Note: We must replace the <ip> with the...
Read more >Incredibly slow (near unusable) on Docker container #1395
I'm using the command jest specs/unit ; which I got from another Jest issue suggesting that supplying the test folder could speed up...
Read more >Docker images provided by CodeBuild - AWS Documentation
AWS CodeBuild manages the following Docker images that are available in the CodeBuild and AWS CodePipeline consoles. ... The base image of the...
Read more >Troubleshoot common issues - Azure Container Instances
This error is most often encountered when deploying Windows images that are based on Semi-Annual Channel release 1709 or 1803, which are not ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
~The segment store starts on port 6000 by default on the standalone.~
This issue is releated to WSL2 and docker on windows.
I have the intuition that this issue also forbid MacOS X development 😢
Running in docker-compose or with testcontainer lead to the same situation where scope and stream can be created, but stream cannot be appended (hangs).
Same code works smoothly if Pravaga runs outside docker.
Any chance to see a fix ?