> ## Documentation Index
> Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Demo Packaging a Buildpack
> Learn to package your buildpack by creating a configuration file and using the pack tool to build and distribute your Docker image.
In this lesson, you will learn how to package your buildpack. The process starts by creating a configuration file named package.toml in the root directory of your project. This configuration file instructs the pack tool on where to locate your buildpack code.
## Step 1: Create the package.toml File
Begin by creating a file called package.toml in your project's root directory with the following content:
```toml theme={null}
[buildpack]
uri = "js-buildpack"
```
This configuration tells the pack tool that your buildpack resides in the folder named js-buildpack.
If your buildpack requires additional dependent buildpacks, you can include them in the package.toml file as demonstrated below:
```toml theme={null}
[buildpack]
uri = "js-buildpack"
[[dependencies]]
uri = "samples/buildpacks/hello-moon"
[[dependencies]]
uri = "docker://cnbs/sample-package:hello-world"
```
For this example, no additional dependencies are needed, so the initial simple configuration is sufficient.
## Step 2: Package the Buildpack
Next, package the buildpack by executing the following command. This command names your buildpack image "my-js-buildpack" and points the pack tool to the package.toml file located in your project root:
```bash theme={null}
pack buildpack package my-js-buildpack --config ./package.toml
```
After running the command, you should see an output similar to the following:
```plaintext theme={null}
[exporter] Reusing layer 'buildpacksio/lifecycle:process-types'
[exporter] Adding label 'io.buildpacks.lifecycle.metadata'
[exporter] Adding label 'io.buildpacks.build.metadata'
[exporter] Adding label 'io.buildpacks.project.metadata'
[exporter] Setting default process type 'web'
[exporter] Saving myapp...
[exporter] *** Images (826b95390a10):
[exporter] myapp
[exporter] Adding cache layer 'my-js-buildpack:node-dependencies'
[exporter] Reusing cache layer 'my-js-buildpack:node-js'
[exporter] Successfully built image myapp
```
This output confirms that your buildpack has been successfully packaged into a Docker image.
## Step 3: Verify the Packaged Image
To confirm that the image has been created, list your Docker images by running:
```bash theme={null}
docker images
```
The output should include your newly packaged buildpack image, resembling the following:
```plaintext theme={null}
pack.local/builder/71796564636c657170e
pack.local/builder/7465747486977260570
pack.local/builder/787166d6717a63756579
my-js-buildpack
cnbs/sample-builder
myapp
latest 4217f3dcc8b 44 years ago 192MB
6abc728b2ef 44 years ago 243MB
0adf8920ef6 44 years ago 84.2MB
e2ab749ad5aa 44 years ago 192MB
ba1c5d8ad7df 44 years ago 243MB
7f0ca68075b3 44 years ago 192MB
04bf31c086fc 44 years ago 243MB
f8a9f9645d9 44 years ago 243MB
latest 04c8aa842a 44 years ago 3.52KB
latest 32c7fcb6fa 44 years ago 243MB
jammy 69b96b5c21 44 years ago 192MB
latest 82691b65db 44 years ago 243MB
593bd8d46dfe 44 years ago 243MB
```
## Step 4: Tag and Distribute the Buildpack Image
If you plan to distribute your buildpack image, you must tag the image with the proper repository identifier before pushing it to Docker Hub or another container registry. To tag the image, run:
```bash theme={null}
docker image tag my-js-buildpack sanjeevkt
```
After tagging your image, push it to the designated container registry using the appropriate Docker push command. This final step readies your buildpack for distribution.
Happy building!