github.com/Racer159/jackal@v0.32.7-0.20240401174413-0bd2339e4f2e/docs/4-deploy-a-jackal-package/2-package-sources.md (about)

     1  # Package Sources
     2  
     3  Jackal currently supports consuming packages from the following sources:
     4  
     5  ### Local Tarball Path (`.tar` and `.tar.zst`)
     6  
     7  A local tarball is the default output of `jackal package create` and is a package contained within a tarball with or without [Zstandard](https://facebook.github.io/zstd/) compression.  Compression is determined by a given package's [`metadata.uncompressed` key](https://docs.jackal.dev/docs/create-a-jackal-package/jackal-schema#metadata) within it's `jackal.yaml` package definition
     8  
     9  ### Split Tarball Path (`.part...`)
    10  
    11  A split tarball is a local tarball that has been split into multiple parts so that it can fit on smaller media when traveling to a disconnected environment (i.e. on DVDs).  These packages are created by specifying a maximum number of megabytes with [`--max-package-size`](../2-the-jackal-cli/100-cli-commands/jackal_package_create.md) on `jackal package create` and if the resulting tarball is larger than that size it will be split into chunks.
    12  
    13  ### Remote Tarball URL (`http://` and `https://` )
    14  
    15  A remote tarball is a Jackal package tarball that is hosted on a web server that is accessible to the current machine.  By default Jackal does not provide a mechanism to place a package on a web server, but this is easy to orchestrate with other tooling such as uploading a package to a continuous integration system's artifact storage or to a repository's release page.
    16  
    17  ### Remote OCI Reference (`oci://`)
    18  
    19  An OCI package is one that has been published to an OCI compatible registry using `jackal package publish` or the `-o` option on `jackal package create`.  These packages live within a given registry and you can learn more about them in our [Publish & Deploy Packages w/OCI Tutorial](../5-jackal-tutorials/7-publish-and-deploy.md).
    20  
    21  ## Commands with Sources
    22  
    23  A source can be used with the following commands as their first argument:
    24  
    25  - `jackal package deploy <source>`
    26  - `jackal package inspect <source>`
    27  - `jackal package remove <source>`
    28  - `jackal package publish <source>`
    29  - `jackal package pull <source>`
    30  - `jackal package mirror-resources <source>`
    31  
    32  :::note
    33  
    34  In addition to the traditional sources outlined above, there is also a special "Cluster" source available on `inspect` and `remove` that allows for referencing a deployed package via its name:
    35  
    36  - `jackal package inspect <package name>`
    37  - `jackal package remove <package name>`
    38  
    39  Additionally, inspecting a package deployed to a cluster will not be able to show the package's SBOMs, as they are not currently persisted to the cluster.
    40  
    41  :::