Closed shyonae closed 3 months ago
I also can't connect to the Web UI. In my case the special thing is that i use MacVLAN:
services: docking-station: image: loolzzz/docking-station container_name: docking-station restart: unless-stopped
# - WEB_PORT=3000
# - SERVER_PORT=3001
ports:
- 3000:3000
networks:
macvlan:
ipv4_address: 192.168.1.125
volumes:
- /data/docker/docking-station/config:/config
- /data/docker/docking-station/data:/data
- /data/docker/docking-station/logs:/logs
- /var/run/docker.sock:/var/run/docker.sock
- /etc/localtime:/etc/localtime:ro
# you should add mount points for each containers' docker-compose file you intend on update using this tool
# i usually put everything in a single neat folder under
- /var/lib/docker/volumes/portainer_data/_data/compose:/mnt/compose-files
networks: macvlan: name: MVLAN-Server external: true
@shyonae
Firstly,
take a look at https://github.com/LooLzzz/docking-station/issues/3#issuecomment-2227306845
regarding this line
- ${DOCKER_COMPOSE_DIR}:/mnt/compose-files
Secondly, try removing 3047:3001
from the ports:
section
Map only the webui port, the backend is not supposed to be mapped
Another option would be to set the WEB_PORT=3046
environment variable in compose,
and then map 3046:3046
@PinguCloud
Please open a new issue with the complete logs,
I'll do my best to help although I'm not too familiar with the macvlan
option
HI, this is my compose:
As you can see, I don't mount the docker.sock directly for security reasons but instead use a proxy. Now, these are my container logs:
When trying to access the Web UI on port 3046 as I mapped since port 3000 is in use, I get this:
I can access any other container normally, also I can access the container at port 3047 and get a 404 error (probably because I'm making a wrong api request, but still, it connects.).
Any ideas?