1 00:00:01,140 --> 00:00:04,980 [Autogenerated] alright, I've saved the best for last updating. 2 00:00:04,980 --> 00:00:07,930 I debated when I would cover this because we have all these 3 00:00:07,930 --> 00:00:11,340 installed scenarios that we went through in this course. 4 00:00:11,340 --> 00:00:12,440 And the fact is, 5 00:00:12,440 --> 00:00:16,690 the the update strategy that you take is dependent on which of 6 00:00:16,690 --> 00:00:20,060 those approaches you take to installing software. 7 00:00:20,060 --> 00:00:22,290 So the install dictates the updates. 8 00:00:22,290 --> 00:00:25,580 So we kind of had to wait to the end because this is largely a 9 00:00:25,580 --> 00:00:29,200 course about installing and configuring and getting your Docker 10 00:00:29,200 --> 00:00:32,240 engine up and running in a Linux environment. 11 00:00:32,240 --> 00:00:33,310 And so, naturally, 12 00:00:33,310 --> 00:00:38,350 the path that you take to install and configure will dictate the path you 13 00:00:38,350 --> 00:00:43,270 take to update that installation and configuration. 14 00:00:43,270 --> 00:00:48,210 For example, if you start out with Santos and the young package manager, 15 00:00:48,210 --> 00:00:51,140 that's what you'll be using for your update process. 16 00:00:51,140 --> 00:00:55,920 If, however you install on a bunch you're Debian or something similar, 17 00:00:55,920 --> 00:01:00,040 you'll be using the app package manager Most likely. 18 00:01:00,040 --> 00:01:02,280 Now that might seem a little bit hyperbolic, 19 00:01:02,280 --> 00:01:05,820 but more specifically there are choices within some of 20 00:01:05,820 --> 00:01:08,580 these environments that are different. 21 00:01:08,580 --> 00:01:14,140 For example, you could use the Docker snap versus the app package. 22 00:01:14,140 --> 00:01:16,630 These are two different roads to go and they probably 23 00:01:16,630 --> 00:01:18,850 would entail different update processes, 24 00:01:18,850 --> 00:01:23,910 and not that At some point in time, you couldn't change which you're using. 25 00:01:23,910 --> 00:01:27,670 In fact, that's probably one of the strong suits of container. 26 00:01:27,670 --> 00:01:30,620 Ization is the ability to lift and shift. 27 00:01:30,620 --> 00:01:33,110 You can literally pick your containers up, 28 00:01:33,110 --> 00:01:34,960 move them to another environment, 29 00:01:34,960 --> 00:01:38,450 and they should operate exactly as they were operating before. 30 00:01:38,450 --> 00:01:41,440 It's the underlying infrastructure that might be different. 31 00:01:41,440 --> 00:01:45,940 And, of course, that might, until some concerns about storage of data. 32 00:01:45,940 --> 00:01:48,200 I'm also hoping that by the time you get to the end that 33 00:01:48,200 --> 00:01:50,340 whatever release you started with that, 34 00:01:50,340 --> 00:01:54,830 there's a least a point update out so you can try out the process of updating, 35 00:01:54,830 --> 00:01:57,730 even if there's nothing breaking or major about it, 36 00:01:57,730 --> 00:01:58,550 just in the spending. 37 00:01:58,550 --> 00:02:03,270 Making this course I know 2010 came out with 20100.1 and got to say, 38 00:02:03,270 --> 00:02:04,740 I'm hoping the same for you. 39 00:02:04,740 --> 00:02:09,050 Don't take a moment and look at the binary installation route 40 00:02:09,050 --> 00:02:12,160 because this highlights a symmetric property. 41 00:02:12,160 --> 00:02:17,410 Voters at a moment ago, I said, How you update depends on how you install Well, 42 00:02:17,410 --> 00:02:20,940 how you install might also depend on how you want to update. 43 00:02:20,940 --> 00:02:23,400 Take the static builds of Docker. 44 00:02:23,400 --> 00:02:26,420 They are wonderful when you don't have a supported package 45 00:02:26,420 --> 00:02:28,880 manager or supported distribution of Linux. 46 00:02:28,880 --> 00:02:30,940 And you just want to get Docker up and running 47 00:02:30,940 --> 00:02:33,380 really good for a test environment, for example, 48 00:02:33,380 --> 00:02:35,950 maybe even great in a supportive environment just to 49 00:02:35,950 --> 00:02:38,570 simplify the installation for testing purposes. 50 00:02:38,570 --> 00:02:40,770 But then the reality creeps in. 51 00:02:40,770 --> 00:02:45,320 As you add, more components is have done in this course configuration files, 52 00:02:45,320 --> 00:02:49,540 maybe system the unit files or some other service managers. 53 00:02:49,540 --> 00:02:52,440 Perhaps you have some client configuration files, 54 00:02:52,440 --> 00:02:55,660 all those bits and pieces that don't come with the binary distribution. 55 00:02:55,660 --> 00:02:56,590 Let's look at that real quick. 56 00:02:56,590 --> 00:02:58,990 So this is the binaries distribution again. 57 00:02:58,990 --> 00:03:03,080 It just has the compressed tar archive that we downloaded 58 00:03:03,080 --> 00:03:06,060 and then extract into this Docker folder, 59 00:03:06,060 --> 00:03:08,440 and then I literally copied these into the path. 60 00:03:08,440 --> 00:03:10,840 So in my case, because of how I approach this, 61 00:03:10,840 --> 00:03:14,440 I probably should have kept track of what I copied into the path. 62 00:03:14,440 --> 00:03:15,490 Maybe I should have linked it, 63 00:03:15,490 --> 00:03:18,740 and instead or use some sort of tool that could keep track of 64 00:03:18,740 --> 00:03:21,610 the state of the system before and after changes so that when 65 00:03:21,610 --> 00:03:22,820 the next release comes out, 66 00:03:22,820 --> 00:03:26,260 I might be aware that one of these pieces is no longer here. 67 00:03:26,260 --> 00:03:28,740 Or maybe it's been blown apart into separate pieces, 68 00:03:28,740 --> 00:03:30,780 and the old version can't be lingering. 69 00:03:30,780 --> 00:03:34,740 So the static binaries approach this is a more manual approached updating 70 00:03:34,740 --> 00:03:36,660 where you really have to know what you're doing because, 71 00:03:36,660 --> 00:03:40,010 for example, you don't wanna lose any configuration follows you set up. 72 00:03:40,010 --> 00:03:42,830 But where you keep track of those that perhaps you're using 73 00:03:42,830 --> 00:03:46,210 Ansel like we did in that example earlier in the course for 74 00:03:46,210 --> 00:03:47,730 configuration management. 75 00:03:47,730 --> 00:03:48,410 Perhaps not. 76 00:03:48,410 --> 00:03:50,610 Perhaps you're copying files out by hand. 77 00:03:50,610 --> 00:03:54,040 So in this case, the static builds approach, 78 00:03:54,040 --> 00:03:57,240 while tantalizing perhaps, for testing for quick, 79 00:03:57,240 --> 00:03:57,660 rapid, 80 00:03:57,660 --> 00:04:00,010 throwaway environments really doesn't seem so 81 00:04:00,010 --> 00:04:01,830 exciting for a production environment. 82 00:04:01,830 --> 00:04:04,420 And so that's why I think the update process can have a 83 00:04:04,420 --> 00:04:08,140 significant impact on how you want to install Docker. 84 00:04:08,140 --> 00:04:11,220 But don't forget we're talking about the underlying infrastructure here. 85 00:04:11,220 --> 00:04:16,060 If your application what runs on top of this is a container, 86 00:04:16,060 --> 00:04:19,660 that's a standard that should operate just fine, 87 00:04:19,660 --> 00:04:22,760 no matter what the underlying infrastructure is. 88 00:04:22,760 --> 00:04:26,540 And at the end of the day, you can lift and shift those things pretty easily, 89 00:04:26,540 --> 00:04:28,670 and what I mean by that with rows to updates, 90 00:04:28,670 --> 00:04:30,880 is that Let's say you went the binaries approach, 91 00:04:30,880 --> 00:04:34,940 but you don't like the update stories, so you go to a package approach. 92 00:04:34,940 --> 00:04:36,720 So create that new environment, 93 00:04:36,720 --> 00:04:40,500 move your containers over and throw away the old one in a clustered environment. 94 00:04:40,500 --> 00:04:42,860 Quite often, that is the update story. 95 00:04:42,860 --> 00:04:45,530 You drain a note of all of its resource is containers, 96 00:04:45,530 --> 00:04:48,470 volumes, etcetera, perform maintenance, for example, 97 00:04:48,470 --> 00:04:50,550 updating and then you throw it away. 98 00:04:50,550 --> 00:04:51,570 If that doesn't work, 99 00:04:51,570 --> 00:04:58,000 or you bring it back online and your orchestrator will move containers and resource is back to that machine.