 Hello, hello. This is not a lightning talk. This is a five minute advertisement for a workshop that I am going to be running this afternoon. And it's mostly self-explanatory and me teaching something that you probably already know, containers are not virtual machines and we should not treat them as such. And this is the topic that I want to bring up again this afternoon in my workshop. For those of you who mostly I guess actually don't know me my name is Paul Adams. I work at Zalando where I work in the search department. So if you ever happen to go to Zalando and search for red shoes it's my job to make sure that you get red shoes and not blue jeans. And at Zalando we care a lot about containers and how we build containers and how containers get deployed. And at the beginning of this year I set myself on a journey to learn from how other organisations build their containers what really looks like best practice these days. And what started off as a mission to learn about best practice and really understand how other people are building their containers and how they make great products that are containerised. This turned into something else. It turned into a project that I called project where did all this stuff come from. The reason being is I discovered pretty quickly that we have a lot of experiences of organisations building containers which really have come from a virtual machine mindset. And one of the containers that I worked on and what I'm going to be talking about this afternoon of course is the next cloud container. Who here has ever pulled or deployed the next cloud container? What was the first thing you noticed about that container? Just from the pull experience. It's big. Who said that? Straight to the top of the class. It's 634 megabytes. As containers go this is pretty meaty. That's not necessarily bad if everything in there is totally necessary. But the first thing I noticed was it was 634 megabytes and this seemed unusually large for an application that's about 170 megs. So I went for an exploration to find out what's inside there and this is no different from quite a lot of projects where I delved inside their containers. So we have 170 megabytes of next cloud. We have 123 megabytes just of base image. Just of Debbie and Jesse. Just the operating system sitting around inside there. The thing that really surprised me, this maybe doesn't surprise you, I don't come from a PHP background, is 260 megabytes of PHP. This seems large. I don't know, maybe it's not, but to me this seems unnecessarily large. And then not forget the very important stuff at the top there. There's 82 megabytes of stuff inside the next cloud docker image. Stuff could be for example, anything that's not PHP or the operating system basically. So not the base image, so Apache, for example. So I took a look at this portfolio of stuff and I asked myself how much of this is necessary and how lean can we actually make the next cloud container experience. For me, I decided let's take a look at what are the very quick wins here, what are the most obvious things I can work on. The first one is basing the container on Debbie and Jesse. You don't really need 123 or 124 megabytes or whatever it is of Debbie and Jesse infrastructure when about 4 megabytes of Alpine Linux will do the same job. The other thing which, again, I don't come from a PHP background but I decided for myself that perhaps having an entire, appeared to be an entire PHP distribution in there was probably a bit overkill. And then of course just look for any general cruft. What's sitting inside the 82 megabytes of stuff? Why do we need, for example, Apache when we can actually save some space using Nginx? Ultimately I just wanted to make the whole thing leaner. I wanted to make the user experience better so that when someone goes and does docker pull next cloud that it doesn't take too long to download, they have this experience of getting up and running very quickly. I went ahead and did a lot of these things. I have my own docker file available on GitHub and the net result is that I managed to build a working container of only 258 megabytes which is a distinctly more streamlined than the 600 and something that the official container has. I'm running a workshop this afternoon. I do not know enough about next cloud to know that what I built is actually a user-friendly, advisable product. But it's certainly a lot more streamlined and from my outsider's view it works, I hope. So I'd like to invite any of you who are interested in, even if you have no docker experience, if you're interested in learning about docker and how to build images. I'm running a workshop this afternoon. Please do come along and particularly those of you who have hardcore next cloud knowledge which I'm assuming is pretty much everybody do come along because we can start punching holes in my actual container and seeing if it's actually a worthy experience. Thanks very much.