I have to pause in the middle of the video to give a like, and looking for more from the same channel. Very logical, just enough details, and very good voices.
thank you for this, just about to start my MCSA 70-740 exam, this helps me understand docker a bit more(already done some labs of course, but just before my start i tend to listen back to the basics). i like the sentence "if your powershell isn't too hot, it soon will be" translated in my mind as git gud or die trying. :)
Great session ! Thank you for sharing this. Question: @13:00 - mentioned that dotnetapp folder have compiled code - is it safe to assume for .net6.0 - everything from publish folder ?
Quick question for something i am confused on. where does a build server fit into this? In the previous organizations I have worked on, the build server typically checks out the code, applies MSBuild and executes any other commands it needs. Does the docker file itself now get built with the build command? If so, what is the output of that? I'm a bit confused how that process works.
No, you would build and publish the Docker image as one or more separate, subsequent steps, ideally using a Dockerfile or docker-compose.yml from the same source repo. Then all future jobs in your build pipeline can easily pull and run the image. Under Continuous Delivery, you should tag the image with the build number, making it easier to ensure your later pipeline jobs are working with the exact same version (well, this works for Jenkins, Team City and Bamboo at least).
So much crap to do one damn thing, docker is crap. It is much easier to just get a windows exe file and get it over with. Ive tried to get into linux/docker and find it exhausting to even install one thing.
As much noise as the container hype thunderstorm makes, it's main use is; web applications. Sure you can use it for other things, but if you watch a video explaining containers, there's a 99.99% that in that video someone will eventually say; "Lets take a web application as an example".
Maybe one day you find that keep churning out more machines won't work anymore and start looking for a solution out of necessity / survival. There are alternatives beside Docker, but the idea is the same. Until then, just apps on host machine would work. Why looking for a fix when there is no problem, right?
I have to pause in the middle of the video to give a like, and looking for more from the same channel. Very logical, just enough details, and very good voices.
Best introduction to Docker on Windows I've seen. 👍
I was ready to give up on docker for windows until I found this video. Sooo informative
Very good primer. To the point and presented in a simple and logical way
thank you for this, just about to start my MCSA 70-740 exam, this helps me understand docker a bit more(already done some labs of course, but just before my start i tend to listen back to the basics).
i like the sentence "if your powershell isn't too hot, it soon will be" translated in my mind as git gud or die trying. :)
Well done, concise, yet good coverage. Thanks Elton.
I realize it's kinda randomly asking but do anybody know of a good website to stream new movies online ?
@Leandro Gage i would suggest flixzone. You can find it by googling :)
@Leland Kane yup, been using Flixzone for since march myself :)
@Leland Kane Thanks, I went there and it seems to work :) I appreciate it!!
@Leandro Gage Glad I could help xD
you covered so much and very precisely. Great!
I always comparing docker with Application Virtualisation like Softgrid or Citrix and it seems you have confirm it. Thank you
not able to pull the image "microsoft/nanoserver", getting error message "microsoft/nanoserver"
Great session ! Thank you for sharing this.
Question: @13:00 - mentioned that dotnetapp folder have compiled code - is it safe to assume for .net6.0 - everything from publish folder ?
Really great content :)
Good one
Awesome
Very coool.
Great video, however the URL compress links don't seem to be working - just an FYI.
awsome
awesome
Quick question for something i am confused on. where does a build server fit into this? In the previous organizations I have worked on, the build server typically checks out the code, applies MSBuild and executes any other commands it needs. Does the docker file itself now get built with the build command? If so, what is the output of that? I'm a bit confused how that process works.
No, you would build and publish the Docker image as one or more separate, subsequent steps, ideally using a Dockerfile or docker-compose.yml from the same source repo. Then all future jobs in your build pipeline can easily pull and run the image. Under Continuous Delivery, you should tag the image with the build number, making it easier to ensure your later pipeline jobs are working with the exact same version (well, this works for Jenkins, Team City and Bamboo at least).
Containers is a fad that will fade away in 3 years from now
nice talk, but content does not match to it's title
So much crap to do one damn thing, docker is crap. It is much easier to just get a windows exe file and get it over with.
Ive tried to get into linux/docker and find it exhausting to even install one thing.
As much noise as the container hype thunderstorm makes, it's main use is; web applications. Sure you can use it for other things, but if you watch a video explaining containers, there's a 99.99% that in that video someone will eventually say; "Lets take a web application as an example".
Maybe one day you find that keep churning out more machines won't work anymore and start looking for a solution out of necessity / survival. There are alternatives beside Docker, but the idea is the same.
Until then, just apps on host machine would work. Why looking for a fix when there is no problem, right?
Awesome