Complete Intro to Containers (feat. Docker) vs Introduction to Next.js, v3

The course stands apart from typical Docker tutorials by opening with a module called "Crafting Containers by Hand," where students manually implement chroot, Linux namespaces, and cgroups before Docker is introduced. This first-principles approach is the most-cited reason learners say the course made containers finally click, rather than just memorising Dockerfile syntax. The curriculum then progresses through Docker images, Dockerfiles, Node.js containerisation, layer caching strategies, Alpine Linux for smaller images, multi-stage builds, distroless containers, static asset optimisation, bind mounts, volumes, dev containers, Docker networking, Docker Compose, and a practical introduction to Kubernetes and Kompose. The open-source companion notes at btholt.github.io/complete-intro-to-containers are freely available under a Creative Commons licence, which allows learners to revisit content without re-watching videos. The course does cover the original version's content well; a v2 update on Frontend Masters addresses cgroups v2 changes and dependency freshness, so learners should verify which version they are accessing. Minor critiques include the relative brevity of the Kubernetes module, which is treated as a brief orientation rather than a deep dive, and the Node.js-heavy examples, which assume JavaScript familiarity even though the container concepts themselves are language-agnostic.

Brian Holt brings over a decade of engineering and product management experience across Netflix, LinkedIn, Reddit, Microsoft (VS Code team), Stripe, Snowflake/Streamlit, and Databricks, giving him genuine production-grade context for every concept he teaches. On Frontend Masters, he has authored more than a dozen "Complete Intro" courses, making him one of the platform's highest-volume and most-reviewed instructors. Learner feedback consistently uses the same descriptors across multiple courses and years: "excellent," "clear," "fun," "great teacher." His containers course specifically is praised for making systems-level Linux concepts approachable to web developers who have never opened a man page. Holt openly acknowledges when a topic is dense — he describes the course as "pretty dense with a lot of systems-level stuff thrown at you in a short time" — but frames each piece incrementally so the cognitive load stays manageable. His tendency to explain the why behind each tool (why cgroups exist, why Alpine saves hundreds of megabytes, why distroless containers matter in CI/CD pipelines) is cited by multiple reviewers as what separates this from documentation-style instruction. The only consistent criticism is that his pace can feel quick for learners coming from a pure frontend background with no prior Linux exposure, and those learners are advised to take his Complete Intro to Linux and the Command-Line first.

Access to the course requires a Frontend Masters subscription, priced at $39 per month or $390 per year (effectively $32.50 per month). The subscription model is the most common source of neutral and negative sentiment across the 38 opinions analysed, as it compares unfavourably to a one-time Udemy purchase for learners who only want a single course. The value calculation improves significantly if the learner is already subscribed for other Frontend Masters content or plans to take additional courses in the same month. Within that framing, reviewers consistently describe the subscription as worthwhile given the breadth and depth of the catalog. The course notes for Complete Intro to Containers are freely published on GitHub and btholt.github.io under a Creative Commons licence, which Holt explicitly designed so that financial barriers do not block access to the curriculum. Learners on a tight budget can follow the full written curriculum for free, losing only the video walkthroughs. Several blog posts note that this free-access policy, combined with the open-source code examples, makes the course more transparent than most paid offerings at a similar price point.

Rather than a single end-to-end application, the course uses a progression of hands-on exercises that directly reinforce each module. Students begin by creating a containerised environment entirely from Linux primitives — chroot, unshare, cgroups — using command-line tools directly in the terminal. Subsequent exercises containerise a real Node.js application, iterating through progressively optimised Dockerfiles: first a basic image, then one with explicit layer ordering for faster rebuilds, then an Alpine-based version that is roughly 80% smaller than the Debian default, then a multi-stage build, then a distroless variant. The Docker Compose module adds a MongoDB service alongside the Node app, creating a practical multi-container scenario that mirrors real development setups. Pre-built Docker images are provided so that slow internet connections do not block workshop progress. Reviewers note the exercises feel production-relevant rather than toy examples, and the GitHub repository (945 stars, 181 forks) demonstrates ongoing community use. The Kubernetes exercises are more abbreviated — primarily using Kompose to convert a Compose file — and learners who want deep Kubernetes practice will need a dedicated course afterwards.

Container knowledge has become a baseline expectation for full-stack and backend developers at most organisations that deploy to the cloud, and this course maps directly to the most common production patterns: writing Dockerfiles for Node.js services, reducing image sizes for faster CI/CD pipelines, using multi-stage builds to separate build and runtime environments, structuring multi-service applications with Docker Compose, and understanding how Kubernetes orchestrates containers at scale. The dev containers module is particularly relevant to modern team workflows, covering how to use containers to create reproducible development environments that eliminate "works on my machine" problems. Holt draws on his experience across Netflix, Reddit, and cloud infrastructure roles at Stripe and Databricks to ground each concept in how it is actually used in production. Multiple blog post reviewers describe going directly from the course to containerising services at work. The Kubernetes coverage is acknowledged as introductory rather than comprehensive, and learners moving into DevOps or platform engineering roles will need further study. For web developers adding Docker competency to an existing JavaScript skill set, however, this is the most practically oriented course in the Frontend Masters catalog.

The course targets Next.js 13+ and is built around the App Router, covering file-based routing, layouts, route groups, React Server Components, server actions, and Prisma-backed data persistence. Learners consistently praise its production-focused selection of topics — Scott Moss explicitly states he only teaches what he uses in production, which keeps the material lean and relevant. The companion GitHub repository (130+ stars, 66 forks) with branch-per-lesson structure is repeatedly cited as a standout resource for quick lookups. A meaningful minority note that the course deliberately omits several Next.js features (useRouter, usePathname, intercepting routes, advanced image optimisation) and that the v3 content has been partially superseded by Next.js 14/15 changes to caching and the dynamicIO model — though older versions remain accessible on the platform.

Scott Moss is a senior software engineer at Netflix and a two-time Y Combinator founder, which gives his production-first framing credibility. Learner feedback across multiple sources consistently uses superlatives: "incredible," "remarkably well-spoken," "complex concepts broken down into clear, manageable steps." Jason Lengstorf of Learn with Jason called him "one of the best teachers out there." Frontend Masters founder Marc Grabanski credits Moss with convincing the platform to keep releasing updated Next.js course versions as the framework evolved. The only instructor criticism that surfaces is that the pace is too brisk for developers who are still consolidating React fundamentals.

Access requires a Frontend Masters subscription at $39/month or $390/year (~$32.50/month). Against that cost, this single course runs roughly 4-5 hours of video, which makes the monthly plan the appropriate entry point for first-timers. The value equation improves substantially when the subscription unlocks the full library: the React & Next.js learning path alone is listed at 40+ hours across seven courses. Multiple long-term subscribers report renewing two to three times per year and consider the ROI immeasurable relative to skill gains. The course notes and GitHub branches are freely accessible without a paid account, offering a partial free tier for budget-constrained learners.

The build-along project is a SaaS-style notes application backed by Prisma and a database, described as "ready for funding" in the course companion site. The project is realistic enough to demonstrate authentication flows, server actions, and data persistence in a single coherent app. However, reviewers who compare it to full-length bootcamp alternatives note that the final deliverable is relatively modest in scope — closer to a polished proof-of-concept than a portfolio centrepiece. The branch-based Git workflow (one branch per lesson with working solutions) is consistently praised as a learning aid, making it easy to recover from dead-ends without rewatching video.

The consistent theme across learner signals is that Scott Moss's production background at Netflix and Y Combinator-backed startups shapes every topic choice. The course prioritises patterns developers actually encounter — form authentication, server-side data fetching, middleware, and Vercel deployment — over exhaustive API coverage. Several learners note that after completing the course they felt confident starting a real Next.js project rather than needing another tutorial. The primary caveat is framework velocity: App Router and server actions have evolved since the v3 recording, and learners working on Next.js 14+ projects may encounter API-level differences that require cross-referencing the official docs.