how to use docker remote API to build images ??which parameters are required?how to write dockerfile location parameter?

I use postmen client

Hello Guys,
I am trying to start Spark service inside a docker container, Getting the below exception while starting the service,

[root@f451a7c9fcf8 sbin]# ./
starting org.apache.spark.deploy.master.Master, logging to /data/enliven/installations/spark-2.1.0-bin-hadoop2.7//logs/spark--org.apache.spark.deploy.master.Master-1-f451a7c9fcf8.out ssh: connect to host port 22: Connection refused

Please help on this

Post has attachment

Post has attachment

Post has attachment

Post has attachment
Tips to Reduce Docker Image Sizes

Docker pictures can without much of a stretch get to 2– 3GB. Here's a few hints that can help diminish their sizes.

1.Utilize a littler base picture

FROM ubuntu

will set you to 128MB on the beginning. Consider utilizing a littler base picture. For each well-suited get installor yum introduce line you include your Dockerfileyou will be expanding the measure of the picture by that library estimate. Understand that you most likely needn't bother with a considerable lot of those libraries you are introducing.

Consider utilizing an elevated base picture (just 5MB in estimate). No doubt, there are elevated labels for the programming dialect you are utilizing. For instance, Python has 2.7-alpine(~50MB) and3.5-alpine(~65MB).

2.Try not to introduce troubleshoot instruments like vim/twist

I see numerous designers introduce vim and twist in their Dockerfile with the goal that they would more be able to effectively troubleshoot their application. Unless your application relies upon it, don't introduce those conditions. Doing as such nullifies the point of utilizing a little base picture.

However, how would I troubleshoot?

One system is to have an advancement Dockerfile and a generation Dockerfile. Amid advancement, have the greater part of the devices you need, and afterward when sending to generation expel the improvement devices.

3.Limit Layers

Each line of a Dockerfile is a stage in the fabricate procedure; a layer that takes up measure. Join your RUN proclamations to decrease the picture measure. Rather than

FROM debian

RUN able get introduce - y <packageA>

RUN able get introduce - y <packageB>


FROM debian

RUN well-suited get introduce - y <packageA> <packageB>

A disadvantage of this approach is that you'll need to reconstruct the whole picture each time you include another library. In the event that you aren't mindful, Docker doesn't modify layers it's now constructed, and it reserves the Dockerfile line by line Try transforming one character of a Dockerfile you've effectively assembled, and afterward reconstruct. You'll see that each progression over that line will be perceived as of now been constructed, however the line you changed (and each line following) will be modified.

A procedure I prescribe is that while being developed and testing conditions, isolate out the RUN summons. Once you're prepared to send to creation, consolidate the RUN proclamations into one line.

4.Use — no-install suggests on well-suited get introduce

Adding — no-introduce recommendsto able get introduce - y can help significantly lessen the size by abstaining from introducing bundles that aren't in fact conditions yet are prescribed to be introduced close by bundles.

apk include orders ought to have- - no-store included.

5.Add rm -rf /var/lib/apt/lists/* to same layer as apt-get installs

Add rm -rf /var/lib/apt/lists/* toward the finish of the able get - y introduce to tidy up after introduce bundles.

For yum, include yum clean all

Additionally, on the off chance that you are introduce wget or twist keeping in mind the end goal to download some bundle, make sure to join them across the board RUN articulation. At that point toward the finish of the run articulation, well-suited get evacuate twist or wget once you never again require them. This guidance goes for any bundle that you just need incidentally.


FromLatest will Lint your Dockerfile and check for much more strides you can perform to lessen your picture estimate.

Having Docker in your resumes will be an added advantage for your growth in tech industry For More Docker Related....

Post has attachment
Overview of AI and Role of NLP in Big Data

Post has attachment
Realtime implementation of Docker projects by exploring different features of Installing Ubuntu Linux and CentOS Linux, Granting Docker Control to Non-root Users, Docker Containers, Network Configuration Files, Dockerfile Instructions, Docker Info. etc

Docker is the principal software containerization platform. Docker Course helps developers to build, ship and run applications, on any platform. From this course, you get a clear picture of

The Rise of the Virtual Machine
Installing and Updating Docker
Major Docker Components
Building from a Dockerfile
Docker Networking
Docker Commands
Related Jobs and Positions in the Industry

Docker Training is well-structured to learn how you can create containerized applications with Docker that are light-weight and portable.

Who should do this course?

As such there are no prerequisites for learning Docker. However, with a number of opportunities in the field, the following job roles will get benefited from this course:

End Users
IT admins
Project Teams
Web Developers
Application Developers
Aspirants aiming for a career in the prospective field.

What projects are included in this course?

An in-depth knowledge of a Docker project ensures all the critical components are well-covered. With this knowledge, you can increase your visibility and enhance your efficiency in drawing real connections among different components of Docker. We will also provide the complete material covering all the aspects of this project.

Post has attachment
Expose and protect Docker remote API with Caddy IP filtering on Docker Swarm mode

Post has attachment
Grab this free eBook - (available today only 16-Aug-2017) and optimize the power of Docker to run your applications quickly and easily.

What You Will Learn:
• Build a Docker image using Dockerfiles
• Push and publish images on Docker Hub
• Run your own private Docker Hub and upload images onto it
• Create and run services inside a container to deploy your applications with ease
• Share data between the Docker host and containers
• Orchestrate multiple containers with Docker Compose
• Test and debug applications inside a Docker container
• Secure your Docker containers with SELinux
Wait while more posts are being loaded