Unable to run the backend in Ubuntu because it misses the docker containers

[Souvlaki42]

I propably don't understand how to build this project locally in my Ubuntu VPS.

I ran the fetch.sh script and it fetches the containers just fine.

I ran the build.sh script which takes longer as expected and finishes just fine after modifying the Dockerfile to resolve some permission errors.

I build the frontend using nodejs and pnpm just fine.

In no point, I see any docker containers start up.

When trying to run the backend, I see errors because it tries to kill some docker containers that doesn't exist.

Am I doing something wrong or the instructions lack a section about actually running the containers needed?

Sorry in advance, if I'm dumb.

[shepmaster]

I ran the fetch.sh script

I ran the build.sh script

You only need to do one or the other of these.

In no point, I see any docker containers start up.

Did you access the playground through a browser and submit a request?

kill some docker containers that doesn't exist.

Yes, that's a known annoyance. Normally I'd hide those warnings, but I'm in the middle of a (very long) debugging session so they are emitted at a higher level. Normally it doesn't matter. This arises because we try to kill the container even when it exits normally because there's generally no harm in making sure.

the instructions lack a section about actually running the containers needed

You don't run any containers by hand — the playground does that for you.

[Souvlaki42]

Did you access the playground through a browser and submit a request?

Silly me. I though that these errors blocked the server from working at all.

You only need to do one or the other of these.

I know, I just wanted to make sure both are working, in case I wanted to modify anything that needed them.

Now, after ignoring the errors and running docker ps -a I realized that no docker containers expose ports and that regardless of me allowing default port 5000 in my VPS firewalls, I still can't access the playground.

[Souvlaki42]

Ok I found it. I just had to set the host variable to 0.0.0.0 instead of the default 127.0.0.1.
i still don't see the containers running again but worked.

[shepmaster]

i still don't see the containers running

Most endpoints of the playground only run a container for a few seconds, however long it takes to handle the request. The only long-running container is when you run some code using a web browser with a WebSocket connection to the server, in which case the container may stay running for up to 45 minutes.

[Souvlaki42]

The reason I wanted to run the playground locally in the first place was to add some crates in the list for personal use. Is it enought to add them in the crate modifications file and build the docker images? Thanks.

[shepmaster]

crate modifications file

Yep, that should be sufficient!

[Souvlaki42]

I did that and didn't work. I added my new crates in the additions list.

[shepmaster]

You'll need to add it to the additions list, then run the top-crates binary, which creates the Cargo.toml file, then build the containers again.

[Souvlaki42]

Thanks for your incredible help!
I suggest you document some stuff in the self hosting land.
I might do it in myself in a PR later and also include the permission bug fix.
Have a nice week!