D
Dokployβ€’6mo ago
riccc

WSL error during installation

I'm using WSL Ubuntu 24.04 and i'm getting this error root@Administrator:/# curl -sSL https://dokploy.com/install.sh | sh Docker already installed Error response from daemon: must specify a listening address because the address to advertise is not recognized as a system address, and a system's IP address to use could not be uniquely identified Error: Failed to initialize Docker Swarm
27 Replies
riccc
ricccOPβ€’6mo ago
(p.s. i'm kinda new to both linux and docker)
riccc
ricccOPβ€’6mo ago
Pretty sure this is the part that's erroring, but i have no idea why
No description
Gabe Vigodi
Gabe Vigodiβ€’6mo ago
@riccc You need to assign the IP address manually, in this case: advertise_addr = "127.0.0.1" . Also don't forget to change the docker container variables
No description
riccc
ricccOPβ€’6mo ago
i'll try
riccc
ricccOPβ€’6mo ago
No description
Gabe Vigodi
Gabe Vigodiβ€’6mo ago
Are you able to login on localhost:3000?
riccc
ricccOPβ€’6mo ago
no if i do docker ps dokploy isnt there ubuntu is basically vanilla i just installed docker and a container for it if you may be wondering ok so i downloaded the install script edited the ip and now it hasnt errored and works no idea what happened i think i somehow got an older version of the install script
riccc
ricccOPβ€’6mo ago
i got it from here, not sure why i did that
Manual Installation | Dokploy
Learn how to manually install Dokploy on your server.
riccc
ricccOPβ€’6mo ago
Let's goo my first deploy worked
Gabe Vigodi
Gabe Vigodiβ€’6mo ago
Awesome, it's only up from here πŸ˜ƒ
riccc
ricccOPβ€’6mo ago
can i ask another thing how do i specify what volumes i want to make available in the containers like i want a folder for files on my host that are accessible (r & w) from the container how would i do that? in dokploy i found you have to use the -v arg in docker cli
Gabe Vigodi
Gabe Vigodiβ€’6mo ago
When using Docker compose, the volumes are defined as:
volumes:
- ../files/{folder on host}:/{folder on container}
volumes:
- ../files/{folder on host}:/{folder on container}
Dokploy Docs https://docs.dokploy.com/docs/core/applications/advanced#volumesmounts https://docs.dokploy.com/docs/core/docker-compose Docker Docs https://docs.docker.com/engine/storage/volumes/
Docker Compose | Dokploy
Learn how to use Docker Compose with Dokploy
Docker Documentation
Volumes
Learn how to create, manage, and use volumes instead of bind mounts for persisting data generated and used by Docker.
Advanced | Dokploy
Learn how to use advanced features in your application.
riccc
ricccOPβ€’6mo ago
oh okay do i need compose or can i also use just docker
Gabe Vigodi
Gabe Vigodiβ€’6mo ago
Both work but I find it easier to use Docker Compose especially when deploying multiple containers
riccc
ricccOPβ€’6mo ago
alr thank you!
Daksh
Dakshβ€’6mo ago
hey @riccc, im running to the same error. how did you manage to fix it? i saw you mentioned you changed the IP, but what exactly did you change?
root@mbpro:~# curl -sSL https://dokploy.com/install.sh | sh
Docker already installed
Node left the swarm.
Error response from daemon: must specify a listening address because the address to advertise is not recognized as a system address, and a system's IP address to use could not be uniquely identified
Error: Failed to initialize Docker Swarm
root@mbpro:~# curl -sSL https://dokploy.com/install.sh | sh
Docker already installed
Node left the swarm.
Error response from daemon: must specify a listening address because the address to advertise is not recognized as a system address, and a system's IP address to use could not be uniquely identified
Error: Failed to initialize Docker Swarm
my error
riccc
ricccOPβ€’6mo ago
um i got the installation script from https://dokploy.com/install.sh i changed line 59 to advertise_addr="127.0.0.1" if i remember correctly
Daksh
Dakshβ€’6mo ago
i tried that and, everything ran but it aint loading ugh
No description
riccc
ricccOPβ€’6mo ago
try 0.0.0.0 maybe
Daksh
Dakshβ€’6mo ago
so even though i did 127.0.0.1 , it apparently deployed to 0.0.0.0 lol
No description
DJKnaeckebrot
DJKnaeckebrotβ€’5mo ago
This actually should be fine. 0.0.0.0:3000->3000 just says that your local machines port 3000 is mapped to the containers port 3000, which is expected. Have you tried to see the logs of that container by using
docker logs <containerId>
docker logs <containerId>
?
Daksh
Dakshβ€’5mo ago
i mean everything's working now. i dont wanna fidget with it and break itπŸ₯²
DJKnaeckebrot
DJKnaeckebrotβ€’5mo ago
up to you πŸ˜„
Daksh
Dakshβ€’5mo ago
DJKnaeckebrot
DJKnaeckebrotβ€’5mo ago
that should be of no concern, mine did the same but everything works
Daksh
Dakshβ€’5mo ago
yep! all my stuff is accessible via 0.0.0.0:xxxx and 127.0.1.1:xxxx
DJKnaeckebrot
DJKnaeckebrotβ€’5mo ago
glad it works πŸ™‚

Did you find this page helpful?