11/5/2022 0 Comments Docker network not found![]() ![]() 'rm -v' should be able to remove the dangling named volumes defined within the scope of the yml.'up' should create any missing pieces.'down' should never remove the network or 'named volumes' or bind-mounts may remove live container volumes and/or may leave containers in 'Exited' state.'create' should create the network, named volumes, and containers.For example, even if I put my war inside my image, how would folks address the db-init problem? What about creating directories within named volumes BEFORE the containers need them? Maybe someone already has a crafty way to solve what I'm after, and I just haven't found what I'm looking for. #DOCKER NETWORK NOT FOUND FULL#Instead of being in the weeds with specific definitions of commands, I would like to see docker-compose do a better job of handling a full life cycle (setUp,do stuff,tearDown) of let's say, the top 10 or so stacks. wth? Conclusion ( my 2 cents on what it should do ): ![]() # hack2 : 1 or more times to initially populate the named volumesĭocker-compose -p foo up -d Goal: see spot runĭocker-compose -p foo ps # <- this part works great, where have you been all my life? Goal: I'm done playing now, so let's clean upĭocker-compose -p foo down # removes the network, but not the named volumes, hmmm Goal: try to remove the volumesĭocker-compose -p foo rm -v # doesn't actually remove the named volumesĭocker-compose -p foo down -v # doesn't remove the named volumes either (bc the network error)ĭocker-compose -p foo up # hack3 : wait, CTRL+C, only ran this to be able to remove the volumes cleanlyĭocker-compose -p foo down -v # Oh! this time it removed the named volumes. So for now, my workflow was really clunky ( as a fresh set of eyes using docker-compose with named volumes ) let's fire this thing up from scratchĭocker-compose -p foo create # bang! this blows up because the of the network errorĭocker-compose -p foo up # hack1 : wait, then CTRL+C, because create didn't make a networkĭocker run. Additionally, I absolutely love the concept of named-volumes for clarity, and I may use data-containers to bundle sets of named-volumes. Likewise, my httpd container doesn't do much good to reverse-proxy to a tomcat container via ajp where the war doesn't exist. My tomcat container not only relies on my postgres container, but tomcat won't start up if the db connection pool points to a database that doesn't exist. My use case is that I want to spin up a stack ( postgres, tomcat, http ) using docker-compose, however there appears to be no clean way to bring the stack up from scratch without hacking at it. I landed here for this issue, as well as differences between "docker-compose -p foo rm -v" and "docker-compose -p foo down -v" Only the later removes Named-Volumes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |