Skip to content

Commit b9247a4

Browse files
committed
Update README.md
1 parent 4fc42e4 commit b9247a4

File tree

1 file changed

+4
-8
lines changed

1 file changed

+4
-8
lines changed

README.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -267,8 +267,7 @@ CMD [ "build/index.handler" ]
267267
> your-lambda latest 05b92630088f 3 seconds ago 483MB
268268
> public.ecr.aws/lambda/nodejs 24 30d41baede74 3 days ago 449MB
269269
> ```
270-
271-
270+
<!-- -->
272271
> [!TIP]
273272
> When running `docker images` you'll notice that we have got a dangling image that looks a bit like this:
274273
>
@@ -531,8 +530,7 @@ docker compose up --abort-on-container-exit --build
531530

532531
> [!NOTE]
533532
> Now, each time we run the containers, Docker is re-building everything and picking up any new changes.
534-
535-
533+
<!-- -->
536534
> [!TIP]
537535
> Even though Docker is technically re-building each and every time, if there are no new changes, Docker will use cached layers resulting in faster executions.
538536
@@ -823,16 +821,14 @@ docker compose down --rmi all
823821

824822
> [!NOTE]
825823
> This stops all services, removes the containers/networks, and deletes all images used by this project (including cURL, LocalStack, and the custom image we built).
826-
827-
824+
<!-- -->
828825
> [!TIP]
829826
> You will likely have a number of dangling images where we've made changes through out this workshop, run the following to clean them up:
830827
>
831828
> ```shell
832829
> docker image prune
833830
> ```
834-
835-
831+
<!-- -->
836832
> [!WARNING]
837833
> If you followed the prerequisites to run `docker load` this command will not actually remove all images, the `lambda/node` and `lambda/python` images still exist.
838834
>

0 commit comments

Comments
 (0)