{"_id":"589dcfad7510ce0f00a982dc","category":{"_id":"577baf92451b1e0e006075ac","__v":0,"project":"5773dcfc255e820e00e1cd4d","version":"5773dcfc255e820e00e1cd50","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-07-05T13:01:06.540Z","from_sync":false,"order":6,"slug":"developer-hub","title":"Developer tools"},"user":"575e85ac41c8ba0e00259a44","project":"5773dcfc255e820e00e1cd4d","__v":0,"githubsync":"","parentDoc":null,"version":{"_id":"5773dcfc255e820e00e1cd50","__v":26,"project":"5773dcfc255e820e00e1cd4d","createdAt":"2016-06-29T14:36:44.812Z","releaseDate":"2016-06-29T14:36:44.812Z","categories":["5773dcfc255e820e00e1cd51","5773df36904b0c0e00ef05ff","577baf92451b1e0e006075ac","577bb183b7ee4a0e007c4e8d","577ce77a1cf3cb0e0048e5ea","577d11865fd4de0e00cc3dab","578e62792c3c790e00937597","578f4fd98335ca0e006d5c84","578f5e5c3d04570e00976ebb","57bc35f7531e000e0075d118","57f801b3760f3a1700219ebb","5804d55d1642890f00803623","581c8d55c0dc651900aa9350","589dcf8ba8c63b3b00c3704f","594cebadd8a2f7001b0b53b2","59a562f46a5d8c00238e309a","5a2aa096e25025003c582b58","5a2e79566c771d003ca0acd4","5a3a5166142db90026f24007","5a3a52b5bcc254001c4bf152","5a3a574a2be213002675c6d2","5a3a66bb2be213002675cb73","5a3a6e4854faf60030b63159","5c8a68278e883901341de571","5cb9971e57bf020024523c7b","5cbf1683e2a36d01d5012ecd"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-02-10T14:35:25.896Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":4,"body":"The SDK uses[ Docker](https://www.docker.com/) to distribute tools for use on Cavatica. Docker is a tool that allows applications and their dependencies to be packaged into discrete runtime environments, called **containers**.\n\n##Containers:\n\nA Docker** container** is a virtual private server. It can host software applications and their dependencies, which can be run from many diverse environments.\n\nUsing Docker ensures that your tools will run on the Platform no matter what format they are in, and removes the possibility of conflicts between your local development environment and the execution environment of the Platform. Since there is no need to conform to any proprietary format when uploading your tools, you can easily run them elsewhere too.\n\n<div align=\"right\"><a href=\"#top\">top</a></div>\n\n##Images:\n\nDocker **images** are read-only files, which are used to produce containers. They are composed of 'layers' of other images, and any change that is made to an image is carried out by adding a new layer. The dependencies of Docker layers define an ordering, and any layer that does not depend on any other layer is called a **base image**. Typically this layer will describe the operating system for the environment.\n\nDocker containers are built from images, but feature a read-write layer on top, so, unlike images, are interactive and can store state. This means that you can run applications inside them. After any executions in your Docker container, you can save a snapshot of the resulting state as another image.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Overview to Docker\",\n  \"body\": \"For an overview of Docker, please see the [Docker website](https://www.docker.com/what-docker).\"\n}\n[/block]\nDocker images can be uploaded to the [Cavatica Image Registry](the-image-registry), where they are referenced by repositories, which correspond to projects on the Platform. Once uploaded, you can run these tools on the Platform. Workflows will execute the tools in series, inside the containers that they are installed in.\n\n<div align=\"right\"><a href=\"#top\">top</a></div>\n\n##THE DOCKER IMAGE REGISTRY\n\nDocker hosts a number of images that you can use to build your containers. These are stored in an online registry called Docker Hub, where they are also organized into repositories. Docker Hub includes repositories that are are administrated by Docker, and contain images in which commonly-used software has been installed, including operating systems. These are typically used as base images. Docker Hub also hosts user repositories, containing images created and uploaded by Docker users. You are free to use images from any Docker Hub repository in building the image you upload to the Cavatica image registry.\n\nYou can also execute tools on Cavatica that are contained in images stored in Docker Hub. However, storing your images in the Cavatica Image Registry rather than in Docker Hub will speed up processing time on the Platform, since the tools will be executed closer to the data they are processing.\n\n<div align=\"right\"><a href=\"#top\">top</a></div>","excerpt":"","slug":"docker-basics","type":"basic","title":"Docker basics"}
The SDK uses[ Docker](https://www.docker.com/) to distribute tools for use on Cavatica. Docker is a tool that allows applications and their dependencies to be packaged into discrete runtime environments, called **containers**. ##Containers: A Docker** container** is a virtual private server. It can host software applications and their dependencies, which can be run from many diverse environments. Using Docker ensures that your tools will run on the Platform no matter what format they are in, and removes the possibility of conflicts between your local development environment and the execution environment of the Platform. Since there is no need to conform to any proprietary format when uploading your tools, you can easily run them elsewhere too. <div align="right"><a href="#top">top</a></div> ##Images: Docker **images** are read-only files, which are used to produce containers. They are composed of 'layers' of other images, and any change that is made to an image is carried out by adding a new layer. The dependencies of Docker layers define an ordering, and any layer that does not depend on any other layer is called a **base image**. Typically this layer will describe the operating system for the environment. Docker containers are built from images, but feature a read-write layer on top, so, unlike images, are interactive and can store state. This means that you can run applications inside them. After any executions in your Docker container, you can save a snapshot of the resulting state as another image. [block:callout] { "type": "info", "title": "Overview to Docker", "body": "For an overview of Docker, please see the [Docker website](https://www.docker.com/what-docker)." } [/block] Docker images can be uploaded to the [Cavatica Image Registry](the-image-registry), where they are referenced by repositories, which correspond to projects on the Platform. Once uploaded, you can run these tools on the Platform. Workflows will execute the tools in series, inside the containers that they are installed in. <div align="right"><a href="#top">top</a></div> ##THE DOCKER IMAGE REGISTRY Docker hosts a number of images that you can use to build your containers. These are stored in an online registry called Docker Hub, where they are also organized into repositories. Docker Hub includes repositories that are are administrated by Docker, and contain images in which commonly-used software has been installed, including operating systems. These are typically used as base images. Docker Hub also hosts user repositories, containing images created and uploaded by Docker users. You are free to use images from any Docker Hub repository in building the image you upload to the Cavatica image registry. You can also execute tools on Cavatica that are contained in images stored in Docker Hub. However, storing your images in the Cavatica Image Registry rather than in Docker Hub will speed up processing time on the Platform, since the tools will be executed closer to the data they are processing. <div align="right"><a href="#top">top</a></div>