You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Unfortunately, I'm unable to connect to the web-ui of ravada.
Ravada is running inside the docker-container on the following machine: OS: Alpine Linux 3.18 Docker version: 23.0.6-r2 docker-compose version: 2.17.3-r2
When connecting to the port 3000 via nc, it says, it's connected:
[user@manjaro ~]$ nc -v 192.168.200.156 3000
Connection to 192.168.200.156 3000 port [tcp/hbci] succeeded!
Where 192.168.200.156 is the host IP of the alpine-linux machine.
According to previous output, I would say, the port on the firewall is open.
I think you mixed 🤪 the two options at the same time.
I recommend Dockers if you want to try a bit of Ravada.
For production it is better to install a server.
If you have any questions ❓ feel free to ask.
Hi @fv3rdugo
Thank you for your answer and sorry for the late response.
Okay, good to know.
Unfortunately, I'm not a big fan of Ubuntu nor Debian.
Since I want to have a hypervisor, that uses as less resources as possible, I chose Alpine.
Do you have a guide to compile it from source which lists the way to go and the dependencies, so I can make my own Alpine package using an APKBUILD (Similar to PKGBUILD from Arch, but for Alpine)?
Describe the bug
Unfortunately, I'm unable to connect to the web-ui of ravada.
Ravada is running inside the docker-container on the following machine:
OS: Alpine Linux 3.18
Docker version: 23.0.6-r2
docker-compose version: 2.17.3-r2
When connecting to the port
3000
vianc
, it says, it's connected:Where
192.168.200.156
is the host IP of the alpine-linux machine.According to previous output, I would say, the port on the firewall is open.
To Reproduce
Steps to reproduce the behavior:
apk add docker docker-cli-compose
IP:3000
Expected behavior
The web-ui should show up and I can login with my admin account
Screenshots
Server (please complete the following information):
Additional context
All containers are up and running, according to the output of
docker compose ps
The text was updated successfully, but these errors were encountered: