what-is-docker-and-how-does-it-work

 

docker-logo

 

In March 2013, Docker was released as open source software and made its debut to the public. Originally, Docker was built as a project within a company called dotCloud whose name later officially became Docker. With its unique architecture, Docker has helped reshape the software industry. Below is a quick guide to what is Docker, how it works, its base architectural elements, and its main advantages.

 

What is Docker?

Docker gives a user the ability to create, ship, and run any application on any infrastructure by using what’s known as containers. It is container architecture, as opposed to the virtual machine alternative, that is able to execute packaged functions with a significant reduction in network latency. In other words, Docker can do the same job but faster. This is, in part, due to the fact that Docker doesn’t require a hypervisor layer and taps directly into the kernel of a host machine.

 

What are the basics of Docker architecture?

Below are some of the basic key concepts used in the Docker domain:

 

  • Dockerfile is a text document of build instructions Docker uses to create an image. The file contains everything that is needed to build up a container including all configuration specs and commands. It’s essentially a recipe for ‘cooking up’ a Docker image.
  • Docker Image is an instruction template for how to create a container. It is a snapshot of the recipe that was in the Dockerfile at a specific point in time.
  • Docker Image Tag is used to identify different versions of an image.
  • Docker Container is the runnable instance of a Docker image. It is an application layer abstraction that contains both the code and its dependencies. The act of running an image creates a container.
  • Docker Repository is a single, centralized location within the Docker domain where container /images/blog are published (pushed), stored, searched, downloaded (pulled), and managed. They can be either remote or on premise or public or private and usually hold multiple versions of a specific image.
  • Docker Registry is an open-source community location that stores a collection of Docker domain based repositories.
  • Docker Hub is a cloud-based version of Docker Registry.
  • Docker Engine is an open source containerization tool that includes a workflow for building and containerizing applications. It provides a universal packaging format that enables applications to run anywhere consistently on any machine utilizing Docker components and services. Docker Engine also creates a server-side daemon process for hosting containers, /images/blog, networks and storage volumes.

 

When should I use Docker and what is its advantage?

Docker assures that applications and systems behave the same regardless of the number of times they have been deployed. It works best with applications that are small and have a singular purpose. As such, Docker forces developers to lean towards creating minimally sized containers. Iterating development with smaller containers reduces complexity favoring predictability and rapid delivery as well as minimizing system drift. Thus it is that one of Docker’s great benefits is allowing for the easy movement and utilization of containers across various on-premise or cloud based systems. It solves the ‘dependency hell’ problem in addition to the annoying and unhelpful co-worker comment, “It works on my laptop”.

 

Conclusion

So what is Docker? In summary, Docker is a leader, with its strongly recommended container minimization and platform agnosticism, that has caused the software industry to shift towards the rise of microservices. The reason it has made such a large contribution is that it simply makes developers lives easier and production schedules drastically shorter.

 

For more information on how to secure the integrity of your Docker /images/blog and containers, check out our blog on how to get free integrity verification for Docker /images/blog.

 

Yes, Take Me to the Blog

 

REFERENCES

https://docs.docker.com

https://blog.codeship.com

https://searchitoperations.techtarget.com/definition/Docker-Hub

https://www.tutorialspoint.com/docker/docker_hub.htm

https://developer.ibm.com/dwblog/2016/what-is-docker-containers/

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.