I watched in 2x, nice video

Great talk

So exactly what did this accomplish? How were Go/Make/Git set up? What can be accessed from the contaner? Can these be used from outside Docker Desktop? Terrible demo.

compose is the best! thanks for your work, it must be an amazing team

his talks are the best 👏

JS is a garbage

Thanks for the walkthrough guys. You made it look very easy and indeed my extension is up & running by 15mins. Khudos..

Great content

Superb...

Thank you :)

please calm down

This was really helpful Peter, thank you.

Thanks for interesting approach using IDE inside a container. Could you explain why you do not use --watch to volume to update code immediately after change on host's mapped volume? What benefits to edit with VSCode in the container instead of the local host filesystem?

This video rocks!! Very nicely said and organised

I have a noob question, why we want to setup a dev environment in a docker?

For 8 years since this video came out. And still he is the only one who explained docker really well thank you very much

Informative and concise. Loved it! :) thanks!

You talk a lot and it all sounds useful but there is very little useful information here for a noob to use to fix vulnerabilities.

So good!

unable to find the github link in the description

I wouldn't give red hat/IBM one dime of our money. We actively cut red hat from our corporation including ansible and couldn't be happier.

To learn how Docker + OpenShift work better together, check out the full video here: kzbin.info/www/bejne/bIenq6enpJWYiJo

To learn how Docker + OpenShift work better together, check out the full video here: kzbin.info/www/bejne/bIenq6enpJWYiJo

Thank you so much for the technology presentation, make it again with Python :D

If you have specific topics or questions about Docker and OpenShift that you'd like us to cover in future videos, let us know!

Life saver!

Hey what is your terminal git prompt configuration? It’s really clean and simple!

Legend!

How does this compare to nixpkgs pkgs.dockerTools.buildImage function that also builds a docker image from a derivation?

Great stuff.

I think radically building the entire image in Nix and only streaming the result may magically fix the cache cost incurred on update (because nix already knows how to) and also results in single-layer minimal images. Single-layer is just more efficient. Oh, and also it keeps all things declarative (the SBOM output can be declarative, as opposed as accidentally being back to imperative because of … well that’s the nature of the copy command in Dockerfiles

Docker Desktop on Windows is using a VM though, so it's only a container on a Linux host.

Amazing video!

Much love brother!

I still don't understand wtf is Moby and why

Agradezco la infirmación que es estupenda para probar la aplicación en mi centro de trabajo donde se cultivan hortalizas, voy a instalar FarmOS en mi propio servidor con docker compose en un entorno con Proxmox.

This was awesome thank you!

Thanks for this! Currently moving a monolith, and my first thought was to refactor into smaller containers from the beginning, but that is not what the business wants. It wants to deliver faster and there is no reason why it can't just be one large container for now, and then subdivided later.

You lost me after 2 Minutes, 2 guys speaking weird English like their head is in a Bucket and a bad dialect behind that! Then i got lost flying thru the pages and settings! Really think you help someone with this crap? No Thanks, and BYEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE....

How do you search in terminal history like this? It seems like an improved Ctrl + R

Is it possible to follow this workshop now without having any expences? E.G. I try to launch an AWS EC2 g5.2xlarge wants ~1.3 USD/h I am not able to follow this wotkshop with the t3.micro from fre Free tier. Also the prerequisites instructs me to choose a "Deep Learning AMI GPU Python 2.0.1, Ubuntu 20.04", the closes I am able to find is "Deep LEarning AMI Neuron (Ubuntu 22.04) 20240226"

Thanks for sharing

Amazing video, but didn't got the solid reason for using --no-cache-dir in pip install, was it to reduce space or something?

I'm stuck at 14:36. I have followed all steps, but when I choose attach to a running container, and select my container, no code pulls through to the new instance. Any ideas? Do I need to do this step?

Where is the deploying part? localhost is not deployment.