Closed a-creation closed 1 year ago
Just validate the example on Fedroa and it works, so it might be M1 related.
Can you run
docker logs carepet-scylla1
and share any error?
I'm on intel mac and experiencing the same thing. I receive the boot-up logs when running that command above, but from clearing and attempting to run bin/migrate/main.rs
over again, I see no new logs are generated from the attempt. This is probably a connectivity issue between localhost and the Docker network being used.
Read this conversation: https://groups.google.com/g/scylladb-users/c/rjz061ECJb8?pli=1
I'm looking into how these docker run
arguments can be worked into the docker-compose.yml
, but please let me know if either of you have any suggestions as well.
After starting three nodes using
docker-compose up -d
and ensuring the three nodes are in UN (up-normal) status, I runNODE1=$(docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' carepet-scylla1) cargo run --bin migrate -- --hosts $NODE1
as stated in the guide. This results in Error: IO Error: No connections in the pool. This is all in the Rust directory of the repo.I'm on a M1 Mac.