Docker Cookbook

116 | Chapter 4: Docker Configuration and Development

---

"readonly": true
...
You are now ready to start your container with 
runc
as root, and you will get a shell
inside your container:
$ sudo runc
#
This is the low-level plumbing of Docker and what should evolve to become the
Open Container standard runtime. You can now explore the configuration file and
see how you can define a start-up command for your container, as well as a network
namespace and various volume mounts.
Discussion
The Open Container Project is good news. In late 2014, CoreOS had started develop‐
ing an open standard for container images, including a new trust mechanism, 
appc
.
CoreOS also developed a container runtime implementation for running 
appc
-based
containers. As part of the OCP, 
appc
developers will help develop the new 
runc
speci‐
fication. This will avoid fragmentation in the container image format and runtime
implementation.
If you look at an application container image (i.e., 
ACI
) manifest, you will see high
similarities with the configuration file obtained from 
runc spec
in the preceding sol‐
ution section. You might see some of the 
rkt
implementation features being ported
back into 
runc
.
If you care about standards, watch the specifications coming out of
the Open Container Project.
See Also
•
The blog post on cloudgear.net that inspired this recipe
• The Open Container 
Project
• The App container 
spec
• The 
rkt
 
runtime
4.6 Introducing runc | 117

---

4.7 Accessing the Docker Daemon Remotely
Problem
The default Docker daemon listens on a local Unix socket, 
/var/run/docker.sock
,
which is accessible only locally. However, you would like to access your Docker host
remotely, calling the Docker API from a different machine.