# Strange behavior with docker-compose run --rm stack is-db init (dial tcp : connect refused) **URL:** \ **Category:** How to get started\ **Created:** [March 15, 2022, 10:57am UTC](https://www.thethingsnetwork.org/forum/t/strange-behavior-with-docker-compose-run-rm-stack-is-db-init-dial-tcp-connect-refused/55866 "2022-03-15T10:57:32Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![storm5050](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/storm5050/32/35697_2.png) [@storm5050](https://www.thethingsnetwork.org/forum/u/storm5050)\ **Post date:** [March 15, 2022, 10:57am UTC](https://www.thethingsnetwork.org/forum/t/strange-behavior-with-docker-compose-run-rm-stack-is-db-init-dial-tcp-connect-refused/55866/1 "2022-03-15T10:57:32Z")
System : Windows10 + Docker with WSL2 with Ubuntu 20.04 Hello so I’ve already setup a server on localhost:1815 and it’s working fine, I’ve wrote what I did so I would be able to do it a second time. I’ve copied in another folder the files from the server that worked fine and deleted folders (acme/blop/.env) and tried to do the procedure again which is just : ```auto docker-compose pull docker-compose run --rm stack is-db init ``` which show me this error : ![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/b/6/b6bbaeb9afb9a6e99d9b0d78e9f378e77c573363.png) I wrote docker-compose run --rm stack is-db init a second time same error : ![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/b/a/ba2188418d63ba8b16357102d5b99225cc2aef34.png) Then I tried again and it worked: ![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/1/5/15b3264e021eb7bd6cced394452c786d6c772bd5.png) Why is it working ? (I use an older tag of The Thing Stack because I had the error “ttn\_lorawan does not exist” with the latest tag) Thanks you