Skip to content
New issue

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

Problems trying to reproduce the demo #25

Open
grgustaf opened this issue Dec 6, 2022 · 0 comments
Open

Problems trying to reproduce the demo #25

grgustaf opened this issue Dec 6, 2022 · 0 comments

Comments

@grgustaf
Copy link

grgustaf commented Dec 6, 2022

Hi, I have a few random questions and comments.

First, from my experimentation I'm not sure you can listen for regular NATS and websocket NATS on the same port? In test/infra/nats.conf, I changed the websocket port to e.g. 5222 and removed the listen line, and only then can the container start up correctly. (If you run docker-compose up as it is now you'll see an address already in use error.)

On the wasmcloud_host web UI, I see the JS host show up in the host list after about a minute. I was hoping a could start an actor in it from there, but when I try to use the default remote echo actor, it hangs for about 30s and then shows no actor started, with no error message.

Next, I saw in the demo video that you start the actor from the JS console from a registry at localhost:5000. I wanted to pull the echo actor from the remote registry and push it to the local one, but I found docker can't pull the image. I found a comment on Slack about using wash reg pull and that does work, I get echo.wasm. Now I'm not sure how to push it into the local registry. Does it still work to use a local Docker registry like this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant