Sockudo On Google Cloud Run

[jamiedruce]

Thanks for picking up where Socketi left off! Looks like an increadibly well written solution (very thankful to see some great documentation too).

I've been trying to get the docker package up and running inside of Googles Cloud Run service, deploying straight from Docker Hub and configuring via ENV variables.

I've kept it simple for now, focusing on a single instance, so just local and memory configuration for adapter, cache and queue.

It deploys impressively quick and looks to be working. I can call /usage fine, and I can send messages via trigger(), but as far as the client goes, i get nothing, no success in subscribing or recieving messages.

I was previously set up with Socketi and also tested with Pusher, to confirm that my general set up is valid, so makes me believe its something to do with the configuration of the server, and possibly Cloud Runs unique requirements.

Enabling debugging i get:

[0m �[32m INFO�[0m �[2msockudo::adapter::handler�[0m�[2m:�[0m �[2msrc/adapter/handler/mod.rs�[0m�[2m:�[0m�[2m231:�[0m Received message from 1729906306.6069236935: event 'pusher:subscribe'
thread 'tokio-runtime-worker' panicked at src/channel/manager.rs:255:18:
Invalid message data

stack backtrace:
0: 0x2a556381a77c - <unknown>
1: 0x2a55633d6263 - <unknown>
2: 0x2a5563819ea2 - <unknown>
3: 0x2a556381a473 - <unknown>
4: 0x2a5563819cc6 - <unknown>
[...]
20: 0x3eed121cbea7 - start_thread
21: 0x3eed11f9fadf - clone
22: 0x0 - <unknown>

Appologies if this is not the best place for this, i dont think its an "issue", more of a figuring out the right options for GCP. Hoping this could inform others if i can get it working, as a realy neat way to have a websocket server up and running in seconds.

[countradooku]

i will update the docker image i think it is not updated.

[countradooku]

@jamiedruce can you try now? It should work

[jamiedruce]

OK, just redeployed, but got sockudo: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory

Have the defaults changed around SSL settings? (we arn't using SSL currently)

[countradooku]

yeah i have seen the problem

[countradooku]

@jamiedruce try now

[countradooku]

"id": "app1",
"key": "key1",
"secret": "secret1",
try with these

[jamiedruce]

But do the env variables mentioned no longer override these as they previously did?

[countradooku]

they are inside the docker container. if you build it manually and add your things there and then run docker compose

[countradooku]

i think i need to investigate this

[countradooku]

@jamiedruce the docker image is build with the exact variables found in this repo