Skip to content

Problems trying to reproduce the demo #25

Description

@grgustaf

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions