{"id":29775,"date":"2015-11-09T16:18:02","date_gmt":"2015-11-09T10:48:02","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=29775"},"modified":"2016-12-19T15:02:51","modified_gmt":"2016-12-19T09:32:51","slug":"docker-user-interface-simple-docker-ui","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/docker-user-interface-simple-docker-ui\/","title":{"rendered":"Docker User Interface using Simple Docker UI App"},"content":{"rendered":"

I have always loved using Docker the traditional way. Running commands like docker run<\/strong> etc. has been the way we use Docker<\/a>. While surfing the internet, I found this chrome app which can be downloaded and installed via google chrome and easily be used for getting a user-interface for your Docker Engine. It simplifies the way we use Docker. Now, we can use Docker by clicks rather than commands. “Docker Simplified<\/strong>”<\/p>\n

Use-Case<\/h3>\n

Simply finding a Docker User Interface tool which is easy to use. I found this on google:
\n\"Screenshot
\nYou can find it here: Link<\/a><\/p>\n

It is a web interface that allows you to interact with the Docker Remote API. It\u2019s written in JAVA Script using the AngularJS framework. So, Let’s see how to install it for Docker running on your local machine. You can follow these steps for any remote server too.<\/p>\n

Installation Steps<\/h3>\n

1. Go to the link I have shared above in the Chrome browser. Then click on ADD TO CHROME:
\n\"ScreenshotYou can find it here as well after adding to chrome that is by typing the following in your chrome address bar:\u00a0chrome:\/\/apps\/<\/strong><\/p>\n

2. Next, you need to make some changes<\/h4>\n

You need to enable Docker Remote API and for that you need to edit \/etc\/default\/docker<\/strong> to allow connections adding (do this where your Docker Engine resides, can be your local machine or a remote server):<\/p>\n

[js]DOCKER_OPTS=’-H tcp:\/\/localhost:2375 -H unix:\/\/\/var\/run\/docker.sock'[\/js]<\/p>\n

Note:\u00a0For secure usage, if you are accessing the Docker Engine present on the local machine then use localhost in the above line else use ISP’s IP when the Docker Engine in on a remote machine.<\/h5>\n

Restart the Docker service using:<\/p>\n

[js]sudo service docker restart[\/js]<\/p>\n

Open your browser and verify you can connect to http:\/\/localhost:2375\/_ping\u00a0 (there is an _ before ping in the URL)<\/p>\n

For connecting to a remote server<\/strong>\u00a0in the above URL just replace localhost with the server’s IP. You should get an OK<\/strong> message. Remember, you need to allow the server to listen at port 2375 to your IP(<\/strong>allow the IP in firewalls or security groups).<\/strong><\/p>\n

On the server if you enter the command:<\/p>\n

service docker status<\/code><\/p>\n

It should show the following:
\n\"Screenshot<\/p>\n

3. Once the above is done, click on LAUNCH APP:
\n\"Screenshot<\/h4>\n

 <\/p>\n

Using Simple Docker UI<\/h3>\n

When you click on LAUNCH APP it will open something like:
\n\"Screenshot<\/p>\n

Make sure the changes you made to the default file I mentioned in installation step 2 are saved, Docker service has been restarted and the service is running. After this, click on “Verify”. It should say “Valid connection”. If it says that the connection of the Docker UI has been made to your local machine’s Docker Engine. Now, just click on save.<\/p>\n

Note: Replace localhost by server IP for a remote server.<\/h5>\n

Let’s head to the home tab. Just click on “Home” on the top left corner. It will show display few things as in the below image:
\n\"Screenshot
\nThis is an overview of Docker on your local machine. It has the connections showing on the right side along with Docker and Docker UI version. In the center, it has an overview of running containers, All containers, and Images. Also, it has Event History in the bottom.<\/p>\n

Now, you can see all the containers clicking on either of the two container options showing (Running containers\/All containers) and it will take you the “Containers” tab adjacent to the “Home” tab. So, you can also go there by clicking on the “Containers” menu. Same is the case for “Images”.<\/p>\n

Lets, see what “Containers” menu has for us:
\n\"Screenshot<\/p>\n

So, it has all the containers listed, segregated into running and stopped\/exited. Let’s see what we can do here. Click on the running container’s container ID:
\n\"Screenshot<\/p>\n

It will open options as shown below:
\n\"Screenshot
\nIt gives you options like\u00a0Stop\u00a0<\/strong>and\u00a0Remove<\/strong>. (You would need to stop the container before removing\/deleting) it. Next, the main thing here it the TTY for the container. \u00a0You are inside the container and you can enter any command you want to execute inside the container:
\n\"Screenshot
\nSince the tool is still in Beta stage, sometimes when you type a command for eg. apt-get update it may show it on the screen like aapptt–ggeett uuppddaattee, but don’t worry it executes properly with no flaws:
\n\"Screenshot<\/p>\n

Next option available is Top\u00a0<\/strong>which shows the top processes running inside the container. Since, it is base Ubuntu image that I used to run this container it shows the following:
\n\"Screenshot<\/p>\n

Now, is the File system changes\u00a0<\/strong>option which shows the following which is self-explanatory:
\n\"Screenshot<\/p>\n

Let’s see what the\u00a0Images\u00a0<\/strong>menu has for us. It will show all the Docker images present on my local machine and allow me to launch new containers too:
\n\"Screenshot<\/p>\n

Click on the Image ID and something like below will pop out:
\n\"Screenshot
\nIt will show you options like Start<\/b> and\u00a0Remove.\u00a0<\/strong>It will also show the\u00a0CMD, ENV\u00a0<\/strong>and\u00a0WorkingDir.\u00a0<\/strong>Here they are empty as this is a base Ubuntu image. Along with all that on the right-hand side it shows\u00a0Container exposed ports, Author, OS and creation date.\u00a0<\/strong>At last, in the bottom it shows the creation history of the Docker image.<\/p>\n

Let’s roll up a Docker container now. Just click on\u00a0Start:
\n<\/strong>\"Screenshot<\/strong><\/p>\n

So, there are basic options like:
\nContainer\u00a0<\/strong>Name, Command(CMD), stdin\/stdout (-i and -t switch)\u00a0<\/strong>and\u00a0Ports to expose\u00a0<\/strong>(All, Custom and None). Select these options and then there are two more important options that it gives:\u00a0Volumes\u00a0<\/strong>and\u00a0Environments.\u00a0<\/strong> We can go through these options one by one:<\/p>\n

Volumes:
\n\"Screenshot
\n<\/strong>It will make the \/mnt\/code<\/strong> directory available inside the container at \/opt\/code<\/strong>. If the \/opt\/code directory does not exist Docker will create one.<\/p>\n

Now, you can also input environment variables by clicking on the\u00a0Environments\u00a0<\/strong>option:
\n\"Screenshot
\nI have used a random variable for example. After this just click on run.<\/p>\n

\"Screenshot<\/p>\n

The container is up and running. So, that is how easy it is to use Docker with Simple Docker UI. Anyone having even little knowledge about Docker can use this app and make full use of Docker with a couple of clicks. Hopefully, more features will be added to the app very soon and I will be back with another blog on the same.<\/p>\n","protected":false},"excerpt":{"rendered":"

I have always loved using Docker the traditional way. Running commands like docker run etc. has been the way we use Docker. While surfing the internet, I found this chrome app which can be downloaded and installed via google chrome and easily be used for getting a user-interface for your Docker Engine. It simplifies the […]<\/p>\n","protected":false},"author":174,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":16},"categories":[1174,1],"tags":[248,2734,1916,1891,1883,2594,2729,2730,2732,2733,379,2735,2731],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/29775"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/174"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=29775"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/29775\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=29775"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=29775"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=29775"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}