Simplify container management with Bitbucket Packages (now generally available)

[#1]

Hey everyone,

We launched Bitbucket Packages today, a native container registry built right into Bitbucket Cloud. This means you can manage source code, pipelines, and now container images all in one place.

Why manage your containers in Bitbucket?

With code, CI/CD and containers all in one tool:

• Developers reduce context switching and stay in the flow for longer

• Your organization can cut down tool costs and management overhead

• Admins can simplify access control by managing permissions across code, CI/CD, and packages all in one place. Package access permissions are automatically inherited from the Bitbucket repository it’s linked to.

What’s included at launch:

• Workspace-level container registry with repository-based permissions

• Seamless Docker CLI integration for push/pull via your pipelines

• Transparent billing and usage tracking, with image and tag deletion tools so you can manage your costs

Coming soon:

• Support for language packages (NPM, Maven, PYPI, and more)

Learn more about what’s new, pricing, and how to get started.

If you have questions or feedback, let us know.

[carl]

This is a great addition for teams already invested in Bitbucket Cloud. Having code, pipelines, and container images under one roof really streamlines day-to-day work and cuts down on the overhead of juggling multiple tools. The inherited permissions are a smart touch, too—less setup and fewer access headaches. Looking forward to seeing the upcoming support for language packages as well.

[Nico]

I'm not sure I understand the pricing, especially the network part : according to the table the premium plan has "7 GB" of included network traffic. If I use a container that's 100MB in one of my pipelines that runs 20 times a day, does that mean I'll use 2GB of network traffic each day just by the pipeline loading the container ?

[Hamreet Kaur]

@Nico yes, that's correct. Every time the pipeline pulls the full container image, it uses 100 MB of your network traffic allowance. So 20 runs a day would consume roughly 2 GB daily just for pulling the container.