If you haven’t registered on yet, please do so at

After creating your account, you can download the CodeNotary CLI  and with the following 4 simple steps you can be sure your /images/blog are always authentic and untampered:


1)  Sign Your Docker Images

Login first:

vcn login

After login, you can sign one or all of your Docker /images/blog using:

vcn sign docker://

All assets are signed as private by default, which means that only you will be able to see your name as the signer. Of course, if you decide to make the details of your signature visible to other developers, you can add the –public switch:

vcn sign –public docker://

2)  Verify Your Docker Images

To verify a docker image, use the command:

vcn verify docker://

Anyone can verify an image with CodeNotary CLI. Signing a file as private or public will change the information returned by the command.

If the asset was signed as private (default settings), the verify command returns:

user@opa50:~$ vcn v docker://zerotrust/parity
Asset:   docker://7d2d42157acdabf4ae46a4815af9037179c871a3b20df628c997af5d452bd7ff
Hash:  7d2d42157acdabf4ae46a4815af9037179c871a3b20df628c997af5d452bd7ff
Date:    2019-05-01 14:00:35 +0000 UTC
Key:     0x2a4d3071a9d12e3886d43890d0dbaa8be60febec
Name: docker://7d2d42157acdabf4ae46a4815af9037179c871a3b20df628c997af5d452bd7ff
Size:    270 MB
Status: "TRUSTED"

If the asset was signed as public, the information about the signer is also displayed, as in the example below:

user@opa50:~$ vcn v docker://zerotrust/parity
Asset:   docker://7d2d42157acdabf4ae46a4815af9037179c871a3b20df628c997af5d452bd7ff
Hash:    7d2d42157acdabf4ae46a4815af9037179c871a3b20df628c997af5d452bd7ff
Date:    2019-05-01 14:00:35 +0000 UTC
Key:     0x2a4d3071a9d12e3886d43890d0dbaa8be60febec
Name:    docker://7d2d42157acdabf4ae46a4815af9037179c871a3b20df628c997af5d452bd7ff
Size:    270 MB
Company: vChain, Inc.
Status: "TRUSTED"

If verification fails, i.e. the image you are verifying was not signed, then a non-zero status error code will appear:

Error: unable to verify hash: no matching asset for hash

3)  Verify Your Container Image Before Running

Once you signed your container /images/blog, you can make image integrity a pre-requisite to your "docker run" command with 1 step:

# run a Docker image only when it can be successfully verified

vcn verify docker://hello-world && docker run hello-world

4)  Verify the Integrity of Running Docker Images

Additionally, CodeNotary allows you to verify the /images/blog of your containers during runtime. Here’s how to do that:

docker ps –format {{.Image}} | xargs printf — ‘docker://%s ‘ | xargs vcn verify



That’s how easy it is to sign and verify your Docker /images/blog and make sure only untampered and authentic /images/blog run in your environments. If you haven’t done so yet, get a free account and try it out yourself.

Thanks to the innovative use of blockchain and smart contract technology, you now can iterate faster, more securely and at lower costs while guaranteeing the safety of your committed assets. Docker and the rest of the compromised communities would have saved themselves and their users a lot in remediation costs and headaches if they had simply been using the CodeNotary vcn tool.


See how you can protect your Docker /images/blog with CodeNotary by clicking below to start your free trial. And bonus, it’s free for OSS and non-commercial users.


Sign Me Up!

Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud

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


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.).


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


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.


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


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, …)


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


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.


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


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.


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.