Introduction

Docker provides remote REST API which is beneficial if you want to connect to a remote docker host. Few of the functions which you can achieve using Docker REST API over a simple browser are

• Create and Manage Containers
• Get low-level information about a container
• Get Container Logs
• Start/Stop container
• Kill a container

Things that didn’t worked

Over the internet, most of the people have suggested editing DOCKER_OPTS variable.

• I changed DOCKER_OPTS in the

  /etc/default/docker

  file but it didn’t have any effect
• Then I tried changing DOCKER_OPTS in the file

  /etc/init/docker.conf

  but again no success.

What really worked for me to enable docker remote API on docker host

• Navigate to /lib/system/system in your terminal and open docker.service file
  

  vi /lib/systemd/system/docker.service

• Find the line which starts with ExecStart and adds  -H=tcp://0.0.0.0:2375 to make it look like
  

  ExecStart=/usr/bin/docker daemon -H=fd:// -H=tcp://0.0.0.0:2375

• Save the Modified File
• Reload the docker daemon
  

  systemctl daemon-reload

• Restart the container
  

  sudo service docker restart

• Test if it is working by using this command, if everything is fine below command should return  a JSON
  

  curl http://localhost:2375/images/json

• To test remotely, use the PC name or IP address of Docker Host

The post How to Enable Docker Remote REST API on Docker Host appeared first on Little Big Extra.

Introduction

If you want to push a docker image to Docker Hub repository, it can be achieved using docker maven plugin from fabric8.io. This plugin lets you build images, start and stop containers and push it to Docker repositories

&nsbp;

1. For the below example, I have used Spring Boot Rest service project which is connected to MongoDB. See below link for reference.
2. Using io.fabric8 plugin, under the plugin section add the io.fabric8 plugin
   

   <plugin>
   	<groupId>io.fabric8</groupId>
   	<artifactId>docker-maven-plugin</artifactId>
   	<version>0.20.0</version>....

   
   
3. We need to first build the image from Dockerfile, this plugin supports all the command which are in Dockerfile and you can directly create a docker image by giving arguments in pom.xml but In my view making docker images from Docker file is much easier and simpler. So we will ask maven plugin in below step to look for Dockerfile in root( project base directory)
   

   <name>springboot-mongo-dockerimage:${project.version}</name>
       <alias>springboot-mongo-dockerimage</alias>
   <build>
       <dockerFileDir>${project.basedir}</dockerFileDir>
   </build>

4. Next we specify the docker registry address
   

   <registry>registry.hub.docker.com/YOUR_DOCKER_HUB_USERNAME</registry>

5. Now we need to add authentication credentials in <authconfig> tag
   

   <authConfig>
   	<username>ENTER YOUR DOCKER HUB USERNAME LIKE abhishek</username>
   	<password>ENTER YOUR DOCKER HUB PASSWORD</password>
   </authConfig>

6. We will add execution phases, where we will push the image
   

   <execution>
   	<id>push</id>
   	<phase>post-integration-test</phase>
   	<goals>
   		<goal>push</goal>
   	</goals>
   </execution>

7. Now run the pom.xml using mvn clean install and check your docker hub repo after some time to see if image has been pushed. If you are pushing the image for first time its gonna take some time  depending on the size of image.

Here is the complete build section from the plugin, hope this help.

<build>
		<plugins>
			<plugin>
				<groupId>org.springframework.boot</groupId>
				<artifactId>spring-boot-maven-plugin</artifactId>
			</plugin>
			<plugin>
				<groupId>io.fabric8</groupId>
				<artifactId>docker-maven-plugin</artifactId>
				<version>0.20.0</version>
				<configuration>
					<registry>registry.hub.docker.com/YOUR_DOCKER_HUB_USERNAME</registry>

					<images>
						<image>
							<name>springboot-mongo-dockerhub:${project.version}</name>
							<alias>springboot-mongo-dockerhub</alias>
							<build>
								<dockerFileDir>${project.basedir}</dockerFileDir>

							</build>
							<run>
								<namingStrategy>alias</namingStrategy>
								<dependsOn>
									<container>mongo</container>
								</dependsOn>

								<links>
									<link>mongo</link>
								</links>
								<ports>
									<port>9876:8080</port>
								</ports>
								<log>
									<prefix>TC</prefix>
									<date>default</date>
									<color>cyan</color>
								</log>
							</run>
						</image>
					</images>
					<authConfig>
						<username>ENTER YOUR DOCKER HUB USERNAME LIKE abhishek</username>
						<password>ENTER YOUR DOCKER HUB PASSWORD</password>
					</authConfig>
				</configuration>

				<executions>
					<execution>
						<id>start</id>
						<phase>pre-integration-test</phase>
						<goals>
							<goal>stop</goal>
							<goal>build</goal>
							<goal>start</goal>
						</goals>
					</execution>
					<execution>
						<id>push</id>
						<phase>post-integration-test</phase>
						<goals>
							<goal>stop</goal>
							<goal>push</goal>
						</goals>
					</execution>
				</executions>
			</plugin>
		</plugins>
	</build>

The post How To Push Docker Images To Docker Hub Repository Using Docker Maven plugin appeared first on Little Big Extra.

One of the goals of Continuous Integration andContinuous deployment is that once the code is pushed to the repository it should be tested, built and then packaged for deployment. BitBucket webhook makes is possible to trigger real-time notifications to Jenkins server so the auto build starts as soon as the code is pushed.

Add Jenkins add on to BitBucket server

Once you have installed BitBucket server on your machine, make sure that it is working. The default port is 7990, so you should be able to access it by using localhost: 7990.

• Click on Settings and on the left side under ADD-ONS, click on Find new add-ons.
• Search Jenkins and add the plugin

Install BitBucket Plugin in Jenkins

• Make sure Jenkins is up and Running, in my case, it is running on localhost: 8080
• In Jenkins go to Jenkins->Plugin Manager and install BitBucket Plugin and then restart Jenkins.

Configure Jenkins

• Now go the Job, which you have created and under Source Code Management Plugin, give the GIT Clone URL as shown below in the screenshot.
  

•  Under Build, Triggers make sure two boxes are checked
  a. Build when a change is published to BitBucket
  b. Poll SCM

Configure BitBucket

• Now go to BitBucket -> Repositories and select the repo for which are Jenkins has been configured

• Click on the setting (icon on the left-hand side) and then hooks. Edit the Bitbucket Server Webhook to Jenkins
  a. Enter your Jenkins URL
  b. Repo Clone URL: Select the URL and the same protocol which BitBucket is providing you to clone. In case username is missing from the URL, we need to add it manually.I had to use Chrome Developer tools and remove the disabled flag from the input box and then add username manually.
  Ignore above step if the username is in URL
  c. Once it is enabled edit the URL with http://UserName@Server/gitrepo

• Click on Trigger Jenkins if it says successful everything is fine.
  

•  Commit some code and Jenkins should automatically start the build. Refresh the Jenkins page is auto refresh is disabled

The post How to enable jenkins to auto build with BitBucket server appeared first on Little Big Extra.

Jenkins is a great tool to build and package artifacts, it can be either deployed independently as a service in docker, lets go through the steps required to install Jenkins on docker as a container.

Get official Jenkins Image

• Go to your terminal/command prompt and get the Jenkins latest’s image from docker hub
  

  docker pull Jenkins

Run Docker Image

Map localhost ports

• Then we will try to run the image, we will map Jenkins on localhost port 8080 and port 50000

Map Volumes to persist data

• If it is important to persist the Jenkins data you can choose between the 2 options.
  1. Save data within the docker container, the docker volume persists upon restarts and even after if the container is deleted.
  2. Save data on your host/disk/laptop/machine. Weigh in your requirements and see what fits in with your requirements.
• Option-1> To persist the data within docker container
  

  docker volume create --name jenkins_data
  docker run --name jenkins -d -v jenkins_data:/var/jenkins_home -p 8080:8080 -p 50000:50000 jenkins:latest

OR

• Option-2>To persist the data within host( host machine/laptop) container(option-2)
  

  docker run --name jenkins -d -v /Users/jenkins:/var/jenkins_home -p 8080:8080 -p 50000:50000 jenkins:latest

  Don’t forget to change the path to your local drive  after -v tag /Users/…. in case of Mac and C:/Users…. in case of Windows)

Check Jenkins is running

• Check if docker container Jenkins is running
  

  docker ps -a

  
  If all is fine, it should show output like below
  

  CONTAINER    ID    IMAGE    COMMAND    CREATED   STATUS   PORTS    NAMES
  041465f0254e jenkins:latest "/bin/tini -- /usr..." 43 hours ago Up 58 seconds 0.0.0.0:50000>50000/tcp, 0.0.0.0:8082->8080/tcp jenkins

Configure Jenkins

• Go to Jenkins -> Globals tools configurations and add Java/GIT/Maven installations; download from the internet is an option which you can choose if there are no available installations on your disk as shown below.

The post How to Install Jenkins on Docker appeared first on Little Big Extra.

JFrog Artifactory is a repository manager used for versioning deployable like a jar, war, docker image etc. Artifactory Pro is a licensed/paid version which will let you create repositories for docker images and much more.Artifactory OSS is open source and a restrective version where you can create maven repositories and few others.

Get official Artifactory Image

Pull the Artifactory OSS Docker Image, it’s an open source image. For this tutorial, we will go ahead with Artifactory OSS

docker pull docker.bintray.io/jfrog/artifactory-oss:latest

Run Docker Image

Map localhost ports

• Then we will try to run the image, we will map Docker on localhost port 8081

docker run --name artifactory -d -p 8081:8081 docker.bintray.io/jfrog/artifactory-pro:latest

Map Volumes to persist data

It is important to persist the artifacts which will be fed to Artifactory, so we have two options here

• If it is important to persist the Jenkins data you can choose between the 2 options.
  1. Save data within the docker container, the docker volume persists upon restarts and even after if the container is deleted.
  2. Save data on your host/disk/laptop/machine. Weigh in your requirements and see what fits in with your requirements.

docker stop artifactory
docker rm artifactory

• Option-1> To persist the data within docker container
  

  docker volume create --name artifactory5_data
  
  docker run --name artifactory-5.0.0 -d -v artifactory5_data:/var/opt/jfrog/artifactory -p 8081:8081 docker.bintray.io/jfrog/artifactory-pro:latest

  OR

• Option-2> To persist the data within host( host machine/laptop) container
  

  docker run --name artifactory-5.0.0 -d -v  /Users/abhishek/jfrog/artifactory:/var/opt/jfrog/artifactory -p 8081:8081 docker.bintray.io/jfrog/artifactory-oss:latest

Verify Installation

• Since Artifactory was mapped to localhost port 8081, open your browser and use localhost:8081 if accessing from the same machine.

http://SERVER_DOMAIN:8081/artifactory

The post How to Install Artifactory on Docker appeared first on Little Big Extra.

Maven remote catalogues are very useful in starting a project quickly and neatly. The project structure including src, test directory are created along with pom dependencies.

Follow below steps to add remote archetype catalogue

1. Go to Windows -> Preferences -> Maven ->Archetype
2. Click on Add Remote Catalog
   
3. Add catalogue file as
   • http://repo1.maven.org/maven2/archetype-catalog.xml
4. Description as
   • Remote Archetype catalogue
5. Click on Verify, you should see a message like Found XXX archetype’s

If you are behind a proxy you might need to go to Windows -> Preference-> Network and add the proxy details

Why not use this remote archetype to create your first Spring Boot Project

Follow this Video for more details

The post How to add remote archetype catalog in Eclipse appeared first on Little Big Extra.