From 671edc061fb905d38a9576205a12b8623906aeac Mon Sep 17 00:00:00 2001
From: vmorganp <31448722+vmorganp@users.noreply.github.com>
Date: Wed, 1 Feb 2023 02:03:38 -0700
Subject: [PATCH] use ghcr for README.md demo

---
 README.md           | 2 +-
 docker-compose.yaml | 8 ++++++--
 2 files changed, 7 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 17a5fbe..075bcfd 100644
--- a/README.md
+++ b/README.md
@@ -14,7 +14,7 @@ Monitors network traffic to containers. If there is traffic, the container runs,
     ```
 2. Start the stack
     ```sh
-    DOCKER_BUILDKIT=1 docker-compose up --build
+    docker-compose up
     ```
     This will create 2 containers that you can reach through a third "lazytainer" container
 3. View the running container by navigating to its web ui at `http://localhost:81`. You should see some information about the container
diff --git a/docker-compose.yaml b/docker-compose.yaml
index 712491b..479da83 100644
--- a/docker-compose.yaml
+++ b/docker-compose.yaml
@@ -2,8 +2,12 @@ version: "3"
 services:
   lazytainer:
     container_name: lazytainer
-    # image: ghcr.io/vmorganp/lazytainer:master
-    build: .
+    # to build the image yourself:
+    # 1. comment 'image:...'
+    # 2. uncomment 'build: .'
+    # 3. instead of 'docker compose up', run 'DOCKER_BUILDKIT=1 docker-compose up --build'
+    image: ghcr.io/vmorganp/lazytainer:master
+    # build: .
     environment:
       - VERBOSE=true # probably set this to false unless you're debugging or doing the initial demo
     ports: