[{"_1":2,"_160":-5,"_161":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_139":140},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_88":-5,"_89":90,"_128":-5,"_129":11,"_130":21,"_131":11,"_132":-5,"_133":11,"_134":-5,"_135":136,"_137":91,"_138":-7},"canonicalUrl","https://hub.docker.com/r/jasatwal/catweb/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","jasatwal","reponame","catweb","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":62,"_64":65,"_66":-5,"_67":68,"_69":70,"_71":11,"_72":33,"_73":74,"_79":11,"_80":81,"_85":33,"_86":87},"categories",[],"content_types",[44],"image","date_registered","2019-09-19T19:37:05.094273Z","description","","is_private","last_updated","2021-05-14T07:00:17.920786Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.docker.container.image.v1+json","name","pull_count",9419,"repository_type","star_count",1,"status","status_description","active","source","collaborator_count",0,"full_description","# _Build, Share, Run, any app, anywhere_, with **Docker Enterprise Platform**\n\nThis demo will take you through a process of building and testing a web application locally. We will be using **Docker Desktop Enterprise** `(DDE)` to scaffold an application, we'll then push the docker image up to a private image registry (signing the image using **Docker Content Trust** `(DCT)`), and automatically scan and promote the repository using **Docker Trusted Registry** `(DTR)`. Once we have completed this phase of the development process we will run the web application **Docker Universal Control Plane** `(UCP)` on a **_Kubernetes_** cluster.\n\n> (NB we can also use Docker Swarm as the orchestration engine (works great for Windows workloads as well as Linux based workloads).\n\n## Demo setup\n\n1. Ensure Docker Desktop Enterprise is installed on your machine. If you are using Docker for Windows or Docker for Mac, you're good to go. If not, you can download DDE from https://hub.docker.com/editions/community/docker-desktop-ent\n\n2. Ensure that you have login credentials for Docker Enterprise Platform 3.0 hosted at https://ucp.west.us.se.dckr.org/\n\n3. Create a `respository` named `catweb` within `DTR` (https://dtr.west.us.se.dckr.org/) and set-up `mirroring` to `DockerHub`, a `promotion` to a production namespace, and optionally a webhook to `Slack`.\n\n4. Within a `terminal` set your env variable for `DTR` and login to `DTR`\n\n```bash\n$ export DTR=dtr.west.us.se.dckr.org\n$ echo $DTR\n$ docker login $DTR -u -p \n```\n\n5. **Optional** - _Enable and disable content trust per-shell or per-invocation_\n\nIn a shell, you can enable content trust by setting the DOCKER_CONTENT_TRUST environment variable. Enabling per-shell is useful because you can have one shell configured for trusted operations and another terminal shell for untrusted operations. You can also add this declaration to your shell profile to have it turned on always by default.\n\nTo enable `docker content trust` in a bash shell enter the following commands to set the env var and view it\n\n```bash\n$ export DOCKER_CONTENT_TRUST=1\n$ echo $DOCKER_CONTENT_TRUST\n1\n```\n\n7. Install `Visual Studio Code` from https://code.visualstudio.com/download\n\n## Running the demo\n\nThere are two parts to the demo. The first part will take you through the process of quickly creating a net new cloud native application in a matter of seconds. The process takes you through _scaffolding_ an application based on the **Cloud Native Application Bundle** `(CNAB)` specification using **Docker Application Designer** within `Docker Desktop Enterprise`. The second part will go through the process of using _GitHub_, _DDE_, _DTR_, and _UCP_.\n\nThis demo is designed to show a _build_, _share_, _run_ Docker workflow using a simple Flask-based web app, `catweb`.\n\nThe basic flow is to initially build and run the app locally using Docker Desktop Enterprise, modify the web template to show how hot mounting a volume works, pushing the image to `Docker Trusted Registry` _optionally_ signing the image with `Docker Trusted Registry`, then deploying onto `AWS` using `Docker Universal Control Plane`.\n\n## Build #1 - Application Designer\n\n1. Click the `Moby` icon in your system tray and navigate around the interesting options, explaining each one in turn.\n2. Click `Design new application...`, `Custom application` and explain the different available `services` and associated `ports` etc.\n4. Click the back icon `<` and then select `Choose a template`\n5. Click `Flask / NGINX / MySQL application`, leave the ports as default and click `Continue`\n6. Click a name `demoApp` and select `Scaffold`\n7. Click `Show logs` and describe the process that DDE is going through\n8. Click `Hide logs` (optional), `Run application`, view the application by opening a web browser and entering http://localhost\n9. Click `Open in Visual Studio Code` and describe the folder and file structure, and the docker files that were generated\n10. Run `docker ps` in a terminal to view the running container\n\nWe have not had to learn how to create our Dockerfile(s), docker-compose.yaml, or create the folder and file structure, a bonus being that we have a skeleton application which is up and running in less than a minute.\n\nNow that we have our scaffolded (skeleton) Flash / NGINX / MySQL Server application, we can build upon this and create our net new cloud native application for our project\n\n10. Within the Application Designer UI click `Stop` to stop the application, then click the back `<` chevron\n11. Click the `delete` icon, `confirm and remove application`, and exit `x` the Application Designer UI\n\n## Build #2 - Docker Desktop Enterprise\n\n1. Open a terminal window and change directory to where you want to clone the `catweb` sample `GitHub` repo too.\n\n```bash\n$ cd ~/Documents/Docker/Demonstrations\n$ git clone https://github.com/jas-atwal/catweb.git\nCloning into 'catweb'...\nremote: Enumerating objects: 6, done.\nremote: Counting objects: 100% (6/6), done.\nremote: Compressing objects: 100% (6/6), done.\nremote: Total 291 (delta 2), reused 0 (delta 0), pack-reused 285\nReceiving objects: 100% (291/291), 59.90 KiB | 285.00 KiB/s, done.\nResolving deltas: 100% (161/161), done.\n```\n\nList the files within the directory\n\n```bash\n$ cd catweb\n$ ls\nCOMMANDS.md README.md catweb-deployment.yaml expose-service.yaml src\nDockerfile app.py docker-compose.yml requirements.txt templates\n```\n\n> Notice that we have a `Dockerfile` and a `docker-compose.yaml` file\n\n2. Within `VS Code` open the `catweb` folder, then open the `Dockerfile` and explain the how the app is `built`. You can also show the source code if you wish\n\n3. `Build` the app (explain that Docker is going through each step within the Dockerfile in the specified order), and use the `docker image` command to view the details of the built image\n\n```bash\n$ docker build --no-cache -t catweb .\nSuccessfully built fd80b366dad9\nSuccessfully tagged catweb:latest\nTagging alpine@sha256:72c42ed48c3a2db31b7dafe17d275b634664a708d901ec9fd57b1529280f01fb as alpine:latest\n```\n\nLet's view the generated `image`\n\n```bash\n$ docker image ls | grep catweb\ncatweb latest fd80b366dad9 2 minutes ago 74.1MB\n```\n\n4. Now that the image has been built, we can run the image as a container using `docker-compose`. Open the `docker-compose.yaml` file within `VS Code` and describe the contents. Now let's `run` the app on `Docker Swarm` as the `orchestration engine` using the commands contained within the `docker-compose` file.\n\n```bash\n$ docker-compose up\nWARNING: The Docker Engine you're using is running in swarm mode.\n\nCompose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.\n\nTo deploy your application across the swarm, use `docker stack deploy`.\n\nCreating catweb_web_1 ... done\nAttaching to catweb_web_1\nweb_1 | * Serving Flask app \"app\" (lazy loading)\nweb_1 | * Environment: development\nweb_1 | * Debug mode: on\nweb_1 | * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)\nweb_1 | * Restarting with stat\nweb_1 | * Debugger is active!\nweb_1 | * Debugger PIN: 316-525-960\n```\n\nOpen a second `terminal` and view the running container using\n\n```bash\n$ docker ps\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES\n7c9ba2ff21b2 catweb_web \"python3 /usr/src/ap…\" About a minute ago Up About a minute 0.0.0.0:5000->5000/tcp catweb_web_1\n```\n\n5. Open a web browser and show the app running at http://localhost:5000\n\n6. Open the `templates/index.html` file within `VS Code` and update the `html` tag `

Catweb - Curated Cat Gifs!

` by adding your name\n\n```html\n

Catweb - Jas' Curated Cat Gifs!

\n```\n\n7. `Refresh` the web page at http://localhost:5000 and notice the change.\n\n8. Stop the container using `CTRL+C`\n\n```bash\n^CGracefully stopping... (press Ctrl+C again to force)\nStopping catweb_web_1 ... done\n```\n\n8. Let's test the running of the app within multiple containers (three in our case) using `docker stack deploy`, and `docker swarm` for orchestration. We can check the running containers using `docker ps` or `docker container ls`\n\n**Note** We can also run the containers locally using _Kubernetes_ as the orchestrator\n\n```bash\n$ docker stack deploy -c docker-compose-prod.yml catweb \nCreating network catweb_default\nCreating service catweb_web\n```\n\n10. Let's view the app at http://localhost:5000. Refresh the browser and notice the `Container ID` changes occasionally. This is because we are running three instances of the application in three separate networked containers and the traffic is being load balanced between them.\n\n11. View the three running containers\n\n```bash\n$ docker ps \nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES\n438d7ec74910 catweb:latest \"python3 /usr/src/ap…\" 4 minutes ago Up 4 minutes 5000/tcp catweb_web.1.5bqnigtauc6ewd1jrts10lm7v\na6d46717c3e1 catweb:latest \"python3 /usr/src/ap…\" 4 minutes ago Up 4 minutes 5000/tcp catweb_web.2.uvcfnuaxsyg0wffosupokrt5q\n17665d8af3c3 catweb:latest \"python3 /usr/src/ap…\" 4 minutes ago Up 4 minutes 5000/tcp catweb_web.3.azc8ed275lfeyzwfd1xap38rd\n```\n\n11. Let's bring one of the containers identified in step 11 down and then check to see their `STATUS`\n\n```bash\n$ docker container kill 438d7ec74910\n438d7ec74910\n```\n\n12. Let's check the running containers\n\n```bash\n$ docker ps\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES\n8610e3297c89 catweb:latest \"python3 /usr/src/ap…\" 8 seconds ago Up 4 seconds 5000/tcp catweb_web.1.p9o12hs072rbzfy27cjm10ocr\na6d46717c3e1 catweb:latest \"python3 /usr/src/ap…\" 5 minutes ago Up 5 minutes 5000/tcp catweb_web.2.uvcfnuaxsyg0wffosupokrt5q\n17665d8af3c3 catweb:latest \"python3 /usr/src/ap…\" 5 minutes ago Up 5 minutes 5000/tcp catweb_web.3.azc8ed275lfeyzwfd1xap38rd\n```\n\n> Notice how a new container has been stood up in place of the container that we killed and has only been up a few seconds\n\nWe are now ready to share the image using `Docker Trusted Registry `, during which we will also `sign` and `scan` the image for `vulnerabilities`.\n\n## Share\n\nNow that the docker image has been built and we have successfully tested the running of the `catweb` application locally, we can push the image up to `Docker Trusted Registry` so that we can sign, scan, and promote the image from `dev` through to `production` for final deployment.\n\n1. We need to `tag` the image and then `push` this tagged image to our private registry `(DTR)` ensuring that you use your own namespace (replace se-jasatwal with your namespace)\n\n```bash\n$ docker tag catweb:latest $DTR/se-jasatwal/catweb:latest\n$ docker image ls | grep catweb \ncatweb_web latest cc5142167446 51 minutes ago 74.1MB\ncatweb latest ebbdcec5a92d About an hour ago 74.1MB\ndtr.west.us.se.dckr.org/se-jasatwal/catweb latest ebbdcec5a92d About an hour ago 74.1MB\n```\n\n```bash\n$ docker push $DTR/se-jasatwal/catweb:latest\nThe push refers to repository [dtr.west.us.se.dckr.org/se-jasatwal/catweb]\naa9ff091b287: Pushed \n164e79b62389: Pushed \n2f6e52a272df: Pushed \n8d4536d51aeb: Pushed \n13806d62f1e3: Pushed \n226cecc8e243: Pushed \n03901b4a2ea8: Layer already exists \nlatest: digest: sha256:2d9db17f7849327fe7c53e5e90e3b9c7398820acd189bc24a97536f59742f3c3 size: 1783\nSigning and pushing trust metadata\nEnter passphrase for repository key with ID 7d9b31d: \nSuccessfully signed dtr.west.us.se.dckr.org/se-jasatwal/catweb:latest\n```\n\n> The `DTR` which we are using for this demo is `dtr.west.us.se.dckr.org`\n\n> If you have enabled `DOCKER_CONTENT_TRUST=1` as an `environment variable` then the first time you `push` an image using `content trust` on your system, the session looks like this:\n\n```bash\nSigning and pushing trust metadata\nYou are about to create a new root signing key passphrase. This passphrase\nwill be used to protect the most sensitive key in your signing system. Please\nchoose a long, complex passphrase and be careful to keep the password and the\nkey file itself secure and backed up. It is highly recommended that you use a\npassword manager to generate the passphrase and keep it safe. There will be no\nway to recover this key. You can find the key in your config directory.\nEnter passphrase for new root key with ID fa0e171:\n```\n\nEnter a passphrase when prompted.\n\n> **_Make note of this `passphrase` as it is not retrievable if forgotten._**\n\nOnce complete you will receive a response similar to that below\n\n```bash\nFinished initializing \"dtr.west.us.se.dckr.org/se-jasatwal/catweb\"\nSuccessfully signed dtr.west.us.se.dckr.org/se-jasatwal/catweb:latest\n```\n\n2. In a web browser navigate to https://dtr.west.us.se.dckr.org/. When prompted to log in, please do so\n\nClick on `Repositories` and within the `Filter by: All Namespaces` enter your `namespace` name, select the `catweb` repositories and select the `tag` first to show the image that you just uploaded. Then discuss the automation of:\n\n```text\nimage signing\nimage scanning,\nimage mirroring\nimage promotions and\nwebhooks\n```\n\n![Image of DTR Repo](/images/sign_scan.png)\n\n## Run\n\nNow that the image has been pushed to our private registry, has been signed, scanned, and promoted through to our production namespace, let's run the web application within a container on `Kubernetes` via **Docker Universal Control Plane** `UCP`.\n\n> We can run the container using a `Kubernetes yaml` file or alternatively via the `command line`. We will use the latter!\n\n1. Create a `Kubernetes deployment` using the `image` that you pushed up to `DTR` and check it exists\n\n```bash\n$ kubectl create deployment catweb --image=$DTR/se-jasatwal/catweb\ndeployment.apps/catweb created\n$ kubectl get deploy | grep catweb\ncatweb 1/1 1 1 30s\n```\n> Where `se-jasatwal` is your namespace in `DTR`.\n> If you have not set the `DTR environment variable` please substitute `$DTR` with `dtr.west.us.se.dckr.org`\n\n2. Create a `Kubernetes service` exposing `port 5000` and using type `LoadBalancer`\n\n```bash\n$ kubectl expose deployment catweb --port=5000 --type=LoadBalancer\nservice/catweb exposed\n```\n\n3. Check to see if the container is running\n\n```bash\n$ kubectl get pod | grep catweb\ncatweb-5c6d4b9c95-z8f4f 1/1 Running 0 5m49s\n```\n\n4. Bring back the details of the service so that you can copy the `EXTERNAL IP` address which you will need in the next step\n\n```bash\n$ kubectl get svc\n$ kubectl get svc | grep catweb\ncatweb LoadBalancer 10.96.33.124 a3c5da531eb2111e9a6fb0242ac11000-757615726.us-west-2.elb.amazonaws.com 5000:35435/TCP 3h27m\n```\n\n> If the EXTERNAL_IP is showing as pending, please wait a few seconds and run the `kubectl get svc | grep catweb` command again until it returns a string as above.\n\n5. In a web browser navigate to http://:5000. View your newly deployed production application running on a `Kubernetes cluster` on `AWS` via the `Docker Enterprise Platform`.\n\n> NOTE: the external_ip address in the example above is _a3c5da531eb2111e9a6fb0242ac11000-757615726.us-west-2.elb.amazonaws.com_\n\n6. Show `UCP Dashboard` and navigate around the aspects such as `Access Control`, `Kubernetes Services` and `Pods` etc.\n\n![Image of UCP](/images/ucp.png)\n\n7. Let's scale the application to provide high availability. Replicas can be specificed within the _Kubernetes_ yaml file, however you can also do this via the command line interface. Let's increase the number of running containers hosting an instance of the application to five.\n\n```bash\n$ kubectl scale --replicas=5 deployment/catweb\ndeployment.extensions/catweb scaled\n```\n\n8. Now let's describe the deployment to view how many ReplicaSets we have, we are expecting five `(5/5 replicas created)`\n\n```bash\n$ kubectl describe deployment catweb\nName: catweb\nNamespace: se-jasatwal\nCreationTimestamp: Mon, 14 Oct 2019 12:50:41 +0100\nLabels: app=catweb\nAnnotations: deployment.kubernetes.io/revision: 1\nSelector: app=catweb\nReplicas: 5 desired | 5 updated | 5 total | 5 available | 0 unavailable\nStrategyType: RollingUpdate\nMinReadySeconds: 0\nRollingUpdateStrategy: 25% max unavailable, 25% max surge\nPod Template:\n Labels: app=catweb\n Containers:\n catweb:\n Image: dtr.west.us.se.dckr.org/se-jasatwal/catweb\n Port: \n Host Port: \n Environment: \n Mounts: \n Volumes: \nConditions:\n Type Status Reason\n ---- ------ ------\n Progressing True NewReplicaSetAvailable\n Available True MinimumReplicasAvailable\nOldReplicaSets: \nNewReplicaSet: catweb-5c6d4b9c95 (5/5 replicas created)\nEvents:\n Type Reason Age From Message\n ---- ------ ---- ---- -------\n Normal ScalingReplicaSet 5m25s deployment-controller Scaled up replica set catweb-5c6d4b9c95 to 5\n```\n\n> Review the `Events` section towards the bottom of the output. We have successfully scaled out to five ReplicaSets.\n\n## Congratulations!!! :tada:\n\n**You have successfully _containerised an application, tested it locally, pushed it up to a private registry, signed, scanned, and promoted the image, then deployed the application to Kubernetes_. All using the Docker Enterprise Platform - the only end-to-end secure software supply chain from DEV to PROD!** :grin:\n\n## Post Demo Clean-up!\n\n**Note**: Do this after EACH demo\n\n1. Manually delete running swarm container from UCP\n2. Manually delete tagged catweb:latest image from DTR\n3. Remove all images and containers\n\n```bash\n$ docker image ls | grep catweb\n$ docker image rm dtr.west.us.se.dckr.org/se-jasatwal/catweb\n$ docker image rm catweb\n$ docker ps -a\n7c9ba2ff21b2\n$ docker container rm 7c9ba2ff21b2\n$ kubectl delete deploy catweb\n$ kubectl delete svc catweb\n$ kubectl get pods\ncatweb-5c6d4b9c95-z8f4f\n$ kubectl delete pod catweb-5c6d4b9c95-z8f4f\n$ docker image prune -a\n$ cd ..\n$ rm -R ~$PWD/catweb/\n```\n\n4. Remove the `demoApp` application\n\n```bash\n$ rm -R ~/Documents/Docker/Demonstrations/app-designer/demoApp\n```\n\n**Note**: The location of your `Application Designer` application files will differ from that above\n\n## --------------------------------------------------------------------------\n\n## Instructions for Deploying to Swarm\n\n1. In a web browser navigate to https://ucp.west.us.se.dckr.org/. If prompted to log in, please do so\n\n2. From the left menu, click `Swarm`, then `Services`\n\n3. Click the `Create` button and fill in the following values replacing `se-jasatwal` with your `namespace`\n\n- Image name: `dtr.west.us.se.dckr.org/se-jasatwal/catweb:latest`\n- Under `Network` select `Add Port+`\n- Enter the port numbers `5000`, and `5000` in the `source` and `target` fields respectively\n- Under `Labels` add two lables:\n\t- `interlock.hostname` and `www`\n\t- `interlock.domain` and `catweb.demo`\n\n**Note**: Make sure to click the plus after each one\n\n4. Click `Create`\n\n5. After the container is successfully deployed, navigate in the web browser to http://www.catweb.demo. This will navigate to your newly deployed container running on AWS via Docker Enterprise Platform.\n\n> Congratulations!! :tada:\n","has_starred","hub_user","immutable_tags_settings",{"_75":11,"_76":77},"enabled","rules",[78],".*","is_automated","permissions",{"_82":21,"_83":11,"_84":11},"read","write","admin","user","storage_size",683892485,"orgData","recentTags",[91],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_50":117,"_118":94,"_119":33,"_120":56,"_57":121,"_122":123,"_124":108,"_125":117,"_126":65,"_127":21},"content_type","creator",824532,"full_size",22082211,"id",69432865,"images",[101],{"_102":103,"_104":105,"_106":48,"_107":108,"_109":110,"_111":112,"_113":48,"_114":-5,"_115":96,"_63":65,"_116":-5},"architecture","amd64","digest","sha256:b1f88b1078ccc3d9d11f84086f20a44e8f3acd4d1b907782690940d91458a0c6","features","last_pulled","2026-09-30T15:51:22.754240712Z","last_pushed","2021-05-06T15:57:53Z","os","linux","os_features","os_version","size","variant","2021-05-14T07:00:17.553428Z","last_updater","last_updater_username","media_type","latest","repository",7727054,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":141,"_148":149,"_135":158,"_159":11},{"_40":142,"_42":143,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":144,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":62,"_64":65,"_66":-5,"_67":68,"_69":70,"_71":11,"_72":33,"_73":145,"_79":11,"_80":147,"_85":33,"_86":87},[],[44],[56],{"_75":11,"_76":146},[78],{"_82":21,"_83":11,"_84":11},"tags",{"_150":62,"_151":-5,"_152":-5,"_153":154},"count","next","previous","results",[155],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":156,"_50":117,"_118":94,"_119":33,"_120":56,"_57":121,"_122":123,"_124":108,"_125":117,"_126":65,"_127":21},[157],{"_102":103,"_104":105,"_106":48,"_107":108,"_109":110,"_111":112,"_113":48,"_114":-5,"_115":96,"_63":65,"_116":-5},[],"canDeleteTags","actionData","errors"]

jasatwal/catweb

Tags for jasatwal/catweb