Skip to content

Commit 4fc42e4

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

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -267,6 +267,8 @@ 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+
270272
> [!TIP]
271273
> When running `docker images` you'll notice that we have got a dangling image that looks a bit like this:
272274
>
@@ -529,6 +531,8 @@ docker compose up --abort-on-container-exit --build
529531

530532
> [!NOTE]
531533
> Now, each time we run the containers, Docker is re-building everything and picking up any new changes.
534+
535+
532536
> [!TIP]
533537
> 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.
534538
@@ -819,12 +823,16 @@ docker compose down --rmi all
819823

820824
> [!NOTE]
821825
> 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+
822828
> [!TIP]
823829
> 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:
824830
>
825831
> ```shell
826832
> docker image prune
827833
> ```
834+
835+
828836
> [!WARNING]
829837
> 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.
830838
>

0 commit comments

Comments
 (0)