Get Adobe Flash player


All things Docker

Very proud to announce my first sponsor of my new blog Morpheus Data. I was very lucky to see a demo of Morpheus Data and was wowed by how feature rich the solution is. The person running the demo just happened to be an old friend of mine from Veeam James Smith. Morpheus is full blown CMP/PaaS or PaaS/CMP not which way round you class it but I saw it as a PaaS product. If you ever sat in one of my PaaS presentations you’d know I look for certain characteristics in a PaaS solution and Morpheus is there IMO. At later stage, I’m going to get a chance to play with this product myself but some words from me on the subject:


Morpheus Data is a company that has come to my attention during my research into CMP solutions. From what I can tell so far, Morpheus has the most complete support of both public and private clouds and allows customers to deploy operating systems, applications or containers into any of the supported platforms equally easily. As well as providing a very simple to use self-service portal to deploy these ‘instance’s it also allows you to build application stacks of multiple components and deploy these at the click of a button. The product also has integrations in tools that are very popular in the DevOps world, things like Ansible, Chef, Puppet to allow workflows to be run at deployment time or at any time after an instant or application has been deployed.


Not only does Morpheus claim to make deployments very easy, but the product also offers monitoring, log capture and backup for the instances as well.


The complete list of supported clouds, integrations and infrastructures tools is very extensive and if it can do everything it claims, this could be a very interesting product. “


Watch out for more good stuff from Morpheus Data.


In Docker to allow Docker clients to access the Docker server (daemon) over the network you have to switch the Docker daemon from using a local socket to a tcp port.


First make sure docker is stopped:


$service docker stop


In the training I watched the command was:


$docker –H IPaddress:Port –d &


For example:


$docker –H –d &


2375 being the default non-ssl port.


This didn’t work for me and after digging around I found the latest syntax for this line looks like:


$docker daemon –H &


My advice though is run the daemon on both the socket and the tcp port as for testing its easier when you are on the docker host system. The command to do this is:


$docker daemon –H unix:///var/run/docker.sock –H &


You may receive an error about an existing file that exists in /var/run . I just deleted using:


$rm /var/run/


Then run the previous command again to fire up Docker on both socket and tcp port.


$docker daemon –H unix:///var/run/docker.sock –H &

Hello All.

Welcome to this new blog. I am a veteran blogger in the virtualisation space but I started to reskill in Cloud Native technologies like Cloud Foundry and Docker. So I decided to start blogging about my experience. Watch this space for education and interesting bits on Cloud Native tech.