Add new tutorial about docker based CF apps #18456

beyhan · 2022-05-24T09:30:46Z

No description provided.

MichaelCzcz · 2022-05-24T11:06:07Z

...-cf-understand-docker-application-lifecycle/cp-cf-understand-docker-application-lifecycle.md

+
+In the above code we begin with the official Node image from Docker. We then proceed to add onto this base image, adding files, downloading dependencies, and providing the start command for the `cf-nodejs` app. Make sure to save the file once you have added the code above. Once that is done you then need to tell Docker to build your image. Run the following command (the `username` is your `Dockerhub` username and some commands may require you to enter your `Dockerhub` password):
+
+```


Please add label Shell / Bash

MichaelCzcz · 2022-05-24T11:06:18Z

...-cf-understand-docker-application-lifecycle/cp-cf-understand-docker-application-lifecycle.md

+
+Now that the image is built, you need to push it to a repository on `Dockerhub`. Running the following commands, a repository will be created for your user called `cf-nodejs-app` and your image will be uploaded to it:
+
+```


Please add label Shell / Bash

MichaelCzcz · 2022-05-24T11:06:25Z

...-cf-understand-docker-application-lifecycle/cp-cf-understand-docker-application-lifecycle.md

+
+Finally, once the image has been uploaded, you can push the image to Cloud Foundry (you can replace the name `docker-nodejs` with whatever you want to name your application).
+
+```


Please add label Shell / Bash

MichaelCzcz · 2022-05-24T11:06:32Z

...-cf-understand-docker-application-lifecycle/cp-cf-understand-docker-application-lifecycle.md

+
+Finally, once the application has started you should be able to access the app through a browser and see the same output as when you ran the `cf-nodejs` app using a buildpack. You can also validate that your application is actually using the docker image by running:
+
+```


Please add label Shell / Bash

MichaelCzcz · 2022-05-24T11:08:06Z

...-cf-understand-docker-application-lifecycle/cp-cf-understand-docker-application-lifecycle.md

+CMD [ "node", "server.js" ]
+```
+
+In the above code we begin with the official Node image from Docker. We then proceed to add onto this base image, adding files, downloading dependencies, and providing the start command for the `cf-nodejs` app. Make sure to save the file once you have added the code above. Once that is done you then need to tell Docker to build your image. Run the following command (the `username` is your `Dockerhub` username and some commands may require you to enter your `Dockerhub` password):


Please don't use the "royal we" when you are giving instructions to the user.

MichaelCzcz · 2022-05-24T11:09:23Z

...-cf-understand-docker-application-lifecycle/cp-cf-understand-docker-application-lifecycle.md

+
+[ACCORDION-BEGIN [Step 2 ](Push a Docker based application)]
+
+To see how docker based applications work you will take the [cf-nodejs](https://github.com/SAP-archive/cf-sample-app-nodejs) application you deployed before and create a docker image of it, which you will then deploy. To do this, the first thing you need to do is create a `Dockerfile` in the same directory as your application files. The path to the `Dockerfile` should be `<path-to-cf-sample-app-nodejs>/Dockerfile` Once the file is created, open the `Dockerfile` with your favorite editor, and add the following (lines beginning with `#` are comments explaining what the line below it does):


Docker is spelled with an upper case D

MichaelCzcz · 2022-05-24T11:10:07Z

...-cf-understand-docker-application-lifecycle/cp-cf-understand-docker-application-lifecycle.md

+
+  2. Access to the registry is also required when the application needs to be re-staged or restarted. If the registry is not accessible, these operations will fail. For this reason it is required to re-push your application if the credentials for a private container registry change.
+
+  3. Additionally, when you use a buildpack, your main concern is your application code. The buildpack takes care of the work of downloading dependencies, compiling code, and creating a droplet from which your application can run. However, when using a docker image, you have to do all this yourself (set up the image, define dependencies, provide settings the image/app needs to start, etc.)


Docker is spelled with an upper case D

MichaelCzcz · 2022-05-24T11:10:50Z

...-cf-understand-docker-application-lifecycle/cp-cf-understand-docker-application-lifecycle.md

+
+> In this example `cf-nodejs-app:latest` is used, but in the next section you will see why using the 'latest' image may not always be what you want.
+
+Finally, once the application has started you should be able to access the app through a browser and see the same output as when you ran the `cf-nodejs` app using a buildpack. You can also validate that your application is actually using the docker image by running:


Docker is spelled with an upper case D

MichaelCzcz · 2022-05-24T11:11:03Z

...-cf-understand-docker-application-lifecycle/cp-cf-understand-docker-application-lifecycle.md

+cf app docker-nodejs
+```
+
+You should then see the `docker image` field with the name your docker image next to it, similar to the output below.


Docker is spelled with an upper case D

Add new tutorial about docker based CF apps

90b5918

MichaelCzcz requested changes May 24, 2022

View reviewed changes

MichaelCzcz assigned jmmargo May 24, 2022

Make Docker upper case and add bash labels

0a72894

jmmargo merged commit 65abc59 into sap-tutorials:master May 25, 2022


		In the above code we begin with the official Node image from Docker. We then proceed to add onto this base image, adding files, downloading dependencies, and providing the start command for the `cf-nodejs` app. Make sure to save the file once you have added the code above. Once that is done you then need to tell Docker to build your image. Run the following command (the `username` is your `Dockerhub` username and some commands may require you to enter your `Dockerhub` password):

		```


		Now that the image is built, you need to push it to a repository on `Dockerhub`. Running the following commands, a repository will be created for your user called `cf-nodejs-app` and your image will be uploaded to it:

		```


		Finally, once the image has been uploaded, you can push the image to Cloud Foundry (you can replace the name `docker-nodejs` with whatever you want to name your application).

		```


		Finally, once the application has started you should be able to access the app through a browser and see the same output as when you ran the `cf-nodejs` app using a buildpack. You can also validate that your application is actually using the docker image by running:

		```


		[ACCORDION-BEGIN [Step 2 ](Push a Docker based application)]

		To see how docker based applications work you will take the [cf-nodejs](https://github.com/SAP-archive/cf-sample-app-nodejs) application you deployed before and create a docker image of it, which you will then deploy. To do this, the first thing you need to do is create a `Dockerfile` in the same directory as your application files. The path to the `Dockerfile` should be `<path-to-cf-sample-app-nodejs>/Dockerfile` Once the file is created, open the `Dockerfile` with your favorite editor, and add the following (lines beginning with `#` are comments explaining what the line below it does):


		2. Access to the registry is also required when the application needs to be re-staged or restarted. If the registry is not accessible, these operations will fail. For this reason it is required to re-push your application if the credentials for a private container registry change.

		3. Additionally, when you use a buildpack, your main concern is your application code. The buildpack takes care of the work of downloading dependencies, compiling code, and creating a droplet from which your application can run. However, when using a docker image, you have to do all this yourself (set up the image, define dependencies, provide settings the image/app needs to start, etc.)


		> In this example `cf-nodejs-app:latest` is used, but in the next section you will see why using the 'latest' image may not always be what you want.

		Finally, once the application has started you should be able to access the app through a browser and see the same output as when you ran the `cf-nodejs` app using a buildpack. You can also validate that your application is actually using the docker image by running:

Add new tutorial about docker based CF apps #18456

Add new tutorial about docker based CF apps #18456

Uh oh!

Conversation

beyhan commented May 24, 2022

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!