First make sure Porter is installed. Please see the installation instructions for more info.
Create a new bundle
porter create command to start a new project:
mkdir -p my-bundle/ && cd my-bundle/ porter create
This will create a file called porter.yaml which contains the configuration for your bundle. Modify and customize this file for your application’s needs.
Here is a very basic porter.yaml file:
name: HELLO version: 0.1.0 description: "An example Porter configuration" tag: getporter/porter-hello mixins: - exec install: - exec: description: "Install Hello World" command: bash flags: c: echo Hello World upgrade: - exec: description: "World 2.0" command: bash flags: c: echo World 2.0 uninstall: - exec: description: "Uninstall Hello World" command: bash flags: c: echo Goodbye World
Build the bundle
porter build command will generate the bundle:
Install the bundle
You can then use
porter install to install your bundle:
If you wish to uninstall the bundle, you can use
Publish the bundle
When you are ready to share your bundle, the next step is publishing it to an OCI registry such as Docker Hub or Quay.
You must authenticate with
docker login before publishing the bundle. Make
sure that the
tag listed in your
porter.yaml is a reference to which the
currently logged in user has write permission.
porter publish and porter will push the invocation image and bundle to
the locations specified in the porter.yaml file:
Install from the registry
Now that your bundle is in a registry, anyone can use a CNAB-compliant tool, not just Porter, to install the bundle.
Previously when we use
porter install when we were in the same directory as a porter bundle, we
didn’t specify an installation name to create, so Porter defaulted the
installation to the name of the bundle. This time we will explicitly name the
porter install demo --tag getporter/porter-hello:v0.1.0
porter uninstall demo