0
1
00:00:00,990 --> 00:00:02,180
So develop a bit.
1

2
00:00:02,340 --> 00:00:03,180
Hello.
2

3
00:00:03,180 --> 00:00:09,870
Question is do you have any tips for prototyping on Raspberry Pi with Docker for ease of dev ops on
3

4
00:00:09,900 --> 00:00:11,930
IOT projects.
4

5
00:00:11,970 --> 00:00:15,500
So let's see IO T projects with raspberry pi.
5

6
00:00:15,530 --> 00:00:18,770
So the interesting thing is you can run.
6

7
00:00:18,810 --> 00:00:23,960
So first off yet to think about architecture right the CPA architecture on a Raspberry Pi is not X 86
7

8
00:00:23,970 --> 00:00:24,840
like an intel right.
8

9
00:00:24,840 --> 00:00:26,310
It's an ARM 64 I believe.
9

10
00:00:26,730 --> 00:00:31,590
So the first thing is if you're using Docker from Mac or Docker for Windows right the docker desktop
10

11
00:00:31,590 --> 00:00:40,440
client you can run those arm 64 containers on your local machine just to get make sure your software
11

12
00:00:40,440 --> 00:00:45,060
works right and your docking file works right and all that stuff before you send it over to the Raspberry
12

13
00:00:45,060 --> 00:00:49,230
Pi so that's a huge problem solver right.
13

14
00:00:49,230 --> 00:00:56,060
So that means you can develop your app locally or mess with your apps locally in ARM 64 containers right.
14

15
00:00:56,070 --> 00:01:01,440
So you're going to need to use ALM 64 Frum's in your Docker file and then whatever stuff you need to
15

16
00:01:01,440 --> 00:01:05,220
add into your image you can be building no you can build those locally and you can send them up to a
16

17
00:01:05,220 --> 00:01:06,100
registry.
17

18
00:01:06,240 --> 00:01:06,880
Right.
18

19
00:01:07,050 --> 00:01:12,570
And then jump in your raspberry pi however you want to do that whether it's over USP or you just plug
19

20
00:01:12,570 --> 00:01:18,330
it in directly to you know some sort of K VM solution or you SSA to it over the network however you
20

21
00:01:18,330 --> 00:01:21,650
want to get to it then you would have Docker on that machine.
21

22
00:01:21,670 --> 00:01:28,530
All right on that pie and then you would pull down the images and run them to make sure that they run
22

23
00:01:28,920 --> 00:01:30,960
the way you expect on that raspberry pi.
23

24
00:01:31,020 --> 00:01:38,430
So I am not a Raspberry Pi expert but from my friends that are the sense I get is that it you wouldn't
24

25
00:01:38,430 --> 00:01:43,650
necessarily be developing or creating your containers images rather on the Raspberry Pi you wouldn't
25

26
00:01:43,650 --> 00:01:48,780
necessarily be building it mean even even though you could it's probably easier for to do that all locally
26

27
00:01:48,780 --> 00:01:54,270
on your macro Windows machine and the way that all works by the way is QE IMU
27

28
00:01:59,410 --> 00:02:06,580
so QE EMU is an emulation function feature basically that you can download and use QE you with other
28

29
00:02:06,580 --> 00:02:12,430
things but it's built into Docker with the desktop edition so it allows you to run not just arm but
29

30
00:02:12,430 --> 00:02:18,250
also other types of architectures and processors and it will run those inside your Docker Linux VM in
30

31
00:02:18,250 --> 00:02:24,850
the background transparently and so they'll act like regular x 86 containers and then once you get things
31

32
00:02:25,480 --> 00:02:30,550
rolling in the correct then you would upload your image to a registry that your PI would have access
32

33
00:02:30,550 --> 00:02:33,440
to and then you could pull those images and run them on your PI.
33

34
00:02:33,510 --> 00:02:33,810
Right.
34

35
00:02:33,820 --> 00:02:41,110
I think that's a better workflow than trying to make your PI sort of your your container developer situation
35

36
00:02:41,140 --> 00:02:41,530
right.
36

37
00:02:41,530 --> 00:02:43,660
You technically don't even need the PI to build it.
37

38
00:02:43,690 --> 00:02:46,580
So go check that out.
38

39
00:02:47,670 --> 00:02:53,660
And if you need more resources on that there's a couple of really great people in the armed community.
39

40
00:02:54,630 --> 00:02:56,450
Alex Ellis has a blog.
40

41
00:02:56,670 --> 00:02:58,210
So that's Alex Ellis.
41

42
00:02:58,220 --> 00:03:04,720
Dot IO and I'll throw that your URL in chat.
42

43
00:03:04,720 --> 00:03:12,360
Yeah just in case you weren't aware he does some pretty interesting examples of PI's sort of how to
43

44
00:03:12,360 --> 00:03:13,590
use Docker with PI and all that.
44

45
00:03:13,590 --> 00:03:17,760
He actually builds little raspberry pi clusters for swarm and all that so check out his blog articles
45

46
00:03:17,760 --> 00:03:19,040
for more information.
46

47
00:03:19,050 --> 00:03:21,060
He is a much better resource than I am.