Can build docker image from Drive C and D, But not L on Win 10. And trying to access my MongoDB service
-
This is my first day and 2nd time around using Docker and Visual Studio 2017. I had trouble building my image using drive L, which is a small partition drive I made to develop on. I develop web projects on small drives because it's easier to manage rather than put them all in the projects folder on drive D. I mapped my Documents folder to drive D because I had a small 200Gb SSD boot drive, but had since upgraded it to a TB. So after half a dozen other issues building that I solved, I decided to move the project to my documents folder on drive D, and I finally got my image to work 3/4 way (Could not connect to MongoDB). The .Net Core Angular website comes up on port 443 like it's suppose to. My question is, well I'm wondering what I'm missing to get my web projects on drives other than C or D to build an image. I did go into docker and checked the shared drive letters that I use, but I'm not quite clear on what the shared drives is for. Like for Docker to be able to access other programs that it requires to do it's job. My other question is accessing my MongoDB service on Win10. While developing my Angular App wrapped in .Net Core website, I just used the MongoDB service. Now I'm ready to deploy my app and my goal is to build a Linux server running Docker on Linux. Should this be the time that I say: "Build a MongoDB Docker Container, and a container for my website and link them to communicate" and finish developing this way? In other words, should I get off Win10 and use the Docker for Windows on Win 10 now to host MongoDB and my development image for final development and deployment?
If it ain't broke don't fix it Discover my world at jkirkerx.com