From 9a91ee72455557df970ffe01db84273323f603f1 Mon Sep 17 00:00:00 2001 From: Craig Osterhout <103533812+craig-osterhout@users.noreply.github.com> Date: Thu, 2 Mar 2023 08:52:11 -0800 Subject: [PATCH] Add cli option to get started part 2 (#16807) * add cli option to get start part 2 --- get-started/02_our_app.md | 32 ++++++++++++++++-- .../images/dashboard-two-containers.png | Bin 50634 -> 66178 bytes 2 files changed, 30 insertions(+), 2 deletions(-) diff --git a/get-started/02_our_app.md b/get-started/02_our_app.md index 4b7c8c122c..42dadcbedd 100644 --- a/get-started/02_our_app.md +++ b/get-started/02_our_app.md @@ -135,9 +135,37 @@ Now that you have an image, you can run the application in a [container](../get- At this point, you should have a running todo list manager with a few items, all built by you. -If you take a quick look at your Docker Dashboard, you should see at least one container running that is using the `getting-started` image and on port `3000`. +If you take a quick look at your containers, you should see at least one container running that is using the `getting-started` image and on port `3000`. To see your containers, you can use the CLI or Docker Desktop's graphical interface. - +
+`Y|(s!!bCq4GM&&3^+Zn~PjmXM(v`rw1p`w;orp=fNF>5;^EC`eb+FlaOnJ6)(a
zN%Dx|dZsO!Y#c5MwEy6(zRf}+RCKd5yh5c%`B3TDv#S`zzHyTNz9ZODc(H?TXh#Km
zKeT^5Gk=;n2X(>6d W2B$@ERmSagjb2WKDQ4H(YBw3jJ@2Lf_t~uxM-*Qt-ZuJ
z+-x=91;XHw@$w9OJKypOaLm1m`CfZ^R+;-1M6Qh?@4G7CiF?ESwTx|Fa{A<_OUw|a
zpA4!UBuLVC)RT(@b?-PX^}NB2dRd60#*F}-5C&i-u+WLa5991tk$yx*CwNQRdvz~G
z$?GY_a%M}k3X#Fp*X3{US+6;!t>M&;P()8iJKSy8B0{64_weFQn<@}D1R96b5y
zMA)=c#jaZ^*UJ1uGC