Visible to Intel only — GUID: GUID-9AB5533D-F2F7-4FD9-8F83-CFF854ACCA21
What’s New?
Concepts
Marketplace (QuickStart)
Test Containers
Import Code and Build Containers
Develop Containers in JupyterLab
Enable Cloud Storage
Available Hardware
Frequently Asked Questions
Known Limitations
About containers, helm-charts and docker-compose
Notices and Disclaimers
Provide Feedback
Visible to Intel only — GUID: GUID-9AB5533D-F2F7-4FD9-8F83-CFF854ACCA21
About containers, helm-charts and docker-compose
Containers
Applications with minimal dependencies are packaged and distributed in the form of read-only snapshot container images to ensure your target system environment is always ready to run your application. A running instance of the container image is commonly referred to as a container. This guide and the Container Playground will use build a container or run a container to simplify and clarify the target use.
Dockerfiles
Containers are built with dockerfiles that describe all the commands that contribute to the contents (application source, executable, scripts and dependencies) of the container image. For interactive development, the Container Playground coding environment provides buildah with usage similar to the docker commands to build your containers from dockerfiles.
Helm-charts and Docker-Compose
The container playground supports docker-compose, a YAML file describing configurations to deploy one or more container applications. Alternatively, you can deploy with Helm-charts - a popular mechanism to share, install, and upgrade applications on container orchestration systems like Kubernetes.
NOTE:
With just a few clicks, you can also use the web user-interface to build containers from your application source code and run your applications on Intel® hardware without any prior knowledge of dockerfiles, docker-compose or helm-charts.