-
Notifications
You must be signed in to change notification settings - Fork 928
Description
IMPORTANT: This is a bug report. If you are having problem with deploying a particular app use the deployment issue type.
If you are having problems with deploying a particular app using a customized dockerfile - please change your questions to Dockerfile and post it where appropriate such as StackOverflow. This is a Docker question, not a CapRover specific issue.
What is the problem?
When trying to install CapRover on a Private [local] Network using the following instructions, I'm never able to access port 3000 because the container that hosts the dashboard NEVER exposes/maps port 3000 to the host as shown below.
As you can see, container "captain-captain.1.wk6z1wopfn45ol12pbclz6744" port 3000/tcp is internal only. So there is literally no way to access the CapRover dashboard from another PC on the network unless this is fixed. Unfortunately, it appears all the provisioning and configuration of those containers are baked into the caprover bootstrapping process and I'm not able to correct this oversight.
Commands used to Install CapRover:
echo "{\"skipVerifyingDomains\":\"true\"}" > /captain/data/config-override.json
docker run -e MAIN_NODE_IP_ADDRESS=192.168.1.206 -p 80:80 -p 443:443 -p 3000:3000 -v /var/run/docker.sock:/var/run/docker.sock -v /captain:/captain caprover/caprover
If applicable, content of captain-definition
file:
Steps to reproduce the problem:
Follow instructions @ CapRover on a Private [local] Network.
Answers to the following questions where applicable:
- OS and Version:
root@caprover:~# uname -a
Linux caprover 5.11.22-3-pve #1 SMP PVE 5.11.22-6 (Wed, 28 Jul 2021 10:51:12 +0200) x86_64 x86_64 x86_64 GNU/Linux
- RAM:
root@caprover:~# free -h
total used free shared buff/cache available
Mem: 2.0G 284M 1.6G 264K 167M 1.7G
Swap: 256M 0B 256M