Skip to main content

Install docker on Ubuntu

Step :1  

Open terminal using command Ctrl+T.

Step 2:

Update your existing list of packages.


sudo apt update

Step 3:

Install prerequisite packages which let apt use packages over HTTPS:


sudo apt install apt-transport-https ca-certificates curl software-properties-common

Step 4:

Add GPG key for the official Docker repository to your system:


curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

Step 5:
Add the Docker repository to APT sources:



sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu bioni

Step 6:

Update the package database 


sudo apt update

Step 7:

Make sure you are about to install from the Docker repo instead of the default Ubuntu repo:


apt-cache policy docker-ce

You'll see output like this, although the version number for Docker may be different:




Notice that docker-ce is not installed

Step 8:


Finally, install Docker:


sudo apt install docker-ce


Step 9:


Docker should now be installed, the daemon started, and the process enabled to start on boot. Check that it's running:


sudo systemctl status docker





Installing Docker now gives you not just the Docker service (daemon) but also the docker command line utility,


Step 10:


To view system-wide information about Docker, use:


docker info




This will give you permission error so try with sudo you can check more on how to avoid using sudo everytime


sudo docker info

To check whether you can access and download images from Docker Hub, type:


Step 11:


sudo docker run hello-world




To see the images that have been downloaded to your computer, type:


sudo docker images





The output should look similar to the following:


The hello-world container you ran in the previous step is an example of a container that runs and exits after emitting a test message. Containers can be much more useful than that, and they can be interactive.

After using Docker for a while, you'll have many active (running) and inactive containers on your computer. To view the active ones, use:


sudo docker ps



check latest one


sudo docker ps -l


  

To view all containers — active and inactive, run docker ps with the -a switch:


sudo docker ps -a


Thats all in terms of installing Docker and some basic commands.

Comments

Popular posts from this blog

Extent report plugin for cucumber framework

Extent Reports  are the most popular  reporting  used with Selenium. ExtentReport API makes our life easy to generate interactive  report  with simple configuartions. It supports almost all Java and .NET test frameworks such as TestNG , JUnit , NUnit etc Here we are discussing about  a plugin which is build on  Extent Report specially for Cucumber. This plugin is used to simple out the implementation of  Extent Report  in  Cucumber Framework .  We are creating a maven project to implement the integration of our plugin with cucumber 1. Create new maven project in any tool eclipse/sts/intellij 2. Open pom.xml and update below entries. Step 1 : Add Cucumber Extent Reporter library to Maven Project Add  cucumber-extentsreport <dependency>      <groupId> com.vimalselvam </groupId>      <artifactId> cucumber-extentsreport </artif...

java: You aren't using a compiler supported by lombok, so lombok will not work and has been disabled.

  In order to make projects compile with the existing builds of Lombok processor, as a workaround you can use the flag -Djps.track.ap.dependencies=false which should be added to File | Settings | Build, Execution, Deployment | Compiler | Build process VM options field. This will disable collection of dependencies specified by an annotation processor when Filer methods are called

Execution default of goal org.springframework.boot:spring-boot-maven-plugin:1.2.3.RELEASE:repackage failed: Unable to find main class

Solutions:  Solution 1 : You needed to change the packaging parameter to jar from pom. Also, the repositories , pluginRepositories , the maven-compiler-plugin and the spring-boot-maven-plugin's version and executions weren't needed. Solution 2:  Try mvn install and see if it works Solution 3: Preview: <properties> <!-- The main class to start by executing java -jar --> <start-class> com.mycorp.starter.HelloWorldApplication </start-class> </properties> Solution 4: Enable the main() method in your Application.java. Configure spring-boot-maven-plugin to specify the class with the main class (Spring should find it anyway if you have one, but good to be explicit): Preview: <plugin> <groupId> org.springframework.boot </groupId> <artifactId> spring-boot-maven-plugin </artifactId> <version> ${spring-boot-version} </version>...