Docker is quickly becoming an invaluable development and deployment tool for many organizations. Come and spend the day learning about what Docker is and how to use it. Discover how to integrate it into your workflow and build an environment that works for you and your team. This hands-on training will give you the kick-start needed to begin using Docker effectively.

All attendees of this training will also receive a print copy of Chris Tankersley’s book: Docker for Developers to go along with their conference registration. This book will be delivered during the class.

PLEASE NOTE: This full-day training class takes place on Monday, May 22nd before the conference, our Training Day. A specific ticket to this class must be purchased separately from your conference registration in order to attend it. A lunch is included in the ticket price.

Comments

Comments are closed.

Rated 5

Shawn Rhoney at 10:30 on 23 May 2017

I learned a lot about Docker. Went from knowing nothing about Docker, and quickly became more confident about trying it out in new / existing projects.

Thanks Chris. It was a lot to absorb in short amount of time but you did it with grace and eloquence.

Rated 5

Jay Kelly at 18:44 on 23 May 2017

Great intro to docker. In-depth.

Rated 5

Mark Knapik at 10:15 on 29 May 2017

The intro to docker was wonderful. Chris did a great job of giving us the info we needed to understand what docker was doing, and how to use it.

We never did get a print copy of the book, but if we get an e-book at some point, that would be fine with me.

Rated 5

Anonymous at 15:41 on 5 Jun 2017

Overall really good with lots of great hands on examples integrated well into the training itself. The only improvement I would suggest is planning a little bit more for if someone runs into a hiccup while they're working on the demonstrations.

In my case I hit a snag in the second part where my database wouldn't update and fell back to taking physical notes instead of trying anything else until we hit a point where we switched to a different branch and I was able to start over. (A good way to let someone 'restart' if the tech went wrong.)

I didn't want to slow the class down or call attention to myself once I hit that hangup since I could take notes and get most of it that way. It turned out I needed a command that I'd typoed 5 slides before... which would be pretty easy to fix with one tweak to the demo materials:

* A text file for commands planned to be run in the demo.

That way copy'n'paste is an option to avoid typos or misreading the instructions, and if someone needs to go back to review what the commands are in case they missed one they have the record of what they should have typed and missed.