7 ms·
Container Training
- natsucks 3y agoOne does not simply deploy...
- stargrazer 3y ago[flagged]
- recursive 3y agoI see a 2021 in there.
- ethbr0 3y agoDocker, where 2021 content is 4 years old in 2023.
- cbarrick 3y agoHave best practices changed since 2019? I'm genuinely curious. Should I not consider this learning resource?
- hooverd 3y agoWhere can I learn the latest and greatest container practices?
- benjaminwootton 3y agoCheck out Bret Fishers courses and content - https://www.bretfisher.com/ https://www.bretfisher.com/
- hooverd 3y agoThanks. I'm excited to become a pod person.
- dp-hackernews 3y agoThis guy has pretty comprehensive and well rated courses for docker and kubernetes - keep an eye out for sales with huge value discounts on his courses... https://www.udemy.com/user/mumshad-mannambeth/ https://www.udemy.com/user/mumshad-mannambeth/
- hooverd 3y agoThank you.
- anderspitman 3y agoI used to feel like docker wasn't worth the complexity but I've come around. It strikes a pretty dang good balance. Is kubernetes worth learning if you don't use microservices at work?
- deleted 3y ago[deleted]
- paulgb 3y agoIf you’re interested enough to be curious, it’s worth sitting down for a day with a mini kubernetes distribution and working through the basics of pods, deployments, and services. They are relatively simple conceptually (the hard part is grokking the kubernetes way of doing things) but they give you a feel for the way Kubernetes works.
- jahsome 3y agoI don't think so. It's overkill for most stuff and probably not particularly worth learning until you /need/ to. If you're curious about orchestration concepts in general, something like nomad is a nice way to wade into the pool rather than the whirlpool of obscenity that is k8s.
- bittermandel 3y agoI fully support this! Nomad has a much smaller API surface compared to Kubernetes, at least by default. Expanding Nomad is also much more straight forward.
- abalashov 3y ago+1, Nomad is fantastically simple (but still flexible), and gives you the proper level of insight into the nature of orchestration and distributed container workloads without bogging you down with arbitrary figments of "because Kubernetes" complexity. After spending a day with Nomad, I feel I fully understand how this could get nightmarishly complicated in a Kubernetes way, and what that would look like, and why someone would want that in some situations. All the understanding without pointless but exacting detours.
- ChrisArchitect 3y ago(2018)
- mkl 3y ago> Past workshops [...] 2021
- dp-hackernews 3y agobtw, Jérôme Petazzoni is one of the very early adopters of docker, so while some stuff may seem a bit dated, it'll still be worth looking into...
- jpgvm 3y agoHe was there at the very start at DotCloud and worked on Dockers predecessor and then Docker itself. Early adopter is really underselling how much he contributed.
- smokel 3y agoI wonder if this is an unpopular opinion, but I just don't get why so many people in the industry started using containers where using, say, jars in the JVM would have worked perfectly fine. It seems so much is lost, for no apparent reason. We used to have clean interfaces, architecture independence, pretty good performance, low startup times, low memory usage, and heaps of experience with the JVM or .NET for years. We now seem to have regressed to modularising software into separate unix processes with less strict interfaces, extremely complex dependency chains, and many more moving parts. Obviously, this is all fine if you are actually building systems at enormous scale, but I see this move to containers in all fields, even for applications that run on a single CPU where performance or scalability is not an issue. What would be the reason for this? Is it simply that younger generations need to relearn from their own mistakes? Or is this part of the micro service hype? (Of course I'm not ignorant to some positive aspects of containers, especially for interfacing with databases or web servers, and other unix services.) My problem is mostly with using containers to split even the most straightforward applications, where existing techniques were (at least IMHO) vastly superior.)
- fearface 3y agoYou don't need to split an application into containers, you can have your full app in a container no problem. You can have all your jars in the container. Using containers doesn't mean you know have to split your apps in different ways, it means you ship the runtime, compiled code, whatever libraries are required and all that in a bundle.
- VectorLock 3y agoEvery programming language had its own version of jars, dependency management, etc. that you then need to reproduce everywhere you want those things to run. Containers mostly abstract that away - you just have a container image filled with what you want and you execute it. It also provides a consistent means of isolation. Thats the benefit I see.
- archsurface 3y agoWhich version of the JVM? The one on your machine, my machine, or the server?
- simonjgreen 3y agoIt greatly frustrates me that Docker Swarm fell out of favour leaving a void between single-host Docker and Kubernetes. It makes self hosting docker with a small amount of resilience and orchestration much more challenging.
- mieubrisse 3y agoAgreed, and we're actually trying to bridge this gap at our company Kurtosis! Docker is great for doing dev - fine-grained control over the container, strong predictability guarantees, fast, and relatively lightweight (in comparison with Kubernetes), but you can't run Prod on it unless you start rebuilding Kubernetes primitives like Services from scratch. Our approach has been "build an abstraction over Docker and Kubernetes that can provide the predictability of Docker when you need it (Dev & Test), and the scalability and resilience of k8s when you need it (Prod)", and then handle compiling down to actual Docker & Kubernetes commands. The goal is for the user to have a single environment definition all the way from Dev to Prod, so you don't have to do the dance of "Docker Compose for Dev, Bash on top of Compose for test, and Helm for Prod" (basically this: https://docs.kurtosis.com/assets/images/kurtosis-utility-66539320d2102bbd5e788e65c1d1e89b.png https://docs.kurtosis.com/assets/images/kurtosis-utility-665... )
- Alifatisk 3y agoIs Docker swarms easily reproducable? If so, how?