Add build and push subcommands to cloudchamber

[IRCody]

Describe your change...
Add build and push subcommands to cloudchamber that build a docker image and push to the cloudchamber managed registry using a local docker daemon.

• Tests
  • [] TODO (before merge)
  • Tests included
  • Tests not necessary because:
• E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)
  • [] I don't know
  • Required
  • Not required because: No e2e test for Cloudchamber yet
• Public documentation
  • TODO (before merge)
  • Cloudflare docs PR(s):
  • Documentation not necessary because: product is private only for certain users.

[changeset-bot]

🦋 Changeset detected

Latest commit: 9aa3698

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
wrangler	Minor
@cloudflare/vitest-pool-workers	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13017665530/npm-package-wrangler-7378

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/7378/npm-package-wrangler-7378

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13017665530/npm-package-wrangler-7378 dev path/to/script.js

Additional artifacts:

cloudflare-workers-bindings-extension:

wget https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13017665530/npm-package-cloudflare-workers-bindings-extension-7378 -O ./cloudflare-workers-bindings-extension.0.0.0-vc02b16f0b.vsix && code --install-extension ./cloudflare-workers-bindings-extension.0.0.0-vc02b16f0b.vsix

create-cloudflare:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13017665530/npm-package-create-cloudflare-7378 --no-auto-update

@cloudflare/kv-asset-handler:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13017665530/npm-package-cloudflare-kv-asset-handler-7378

miniflare:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13017665530/npm-package-miniflare-7378

@cloudflare/pages-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13017665530/npm-package-cloudflare-pages-shared-7378

@cloudflare/unenv-preset:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13017665530/npm-package-cloudflare-unenv-preset-7378

@cloudflare/vite-plugin:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13017665530/npm-package-cloudflare-vite-plugin-7378

@cloudflare/vitest-pool-workers:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13017665530/npm-package-cloudflare-vitest-pool-workers-7378

@cloudflare/workers-editor-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13017665530/npm-package-cloudflare-workers-editor-shared-7378

@cloudflare/workers-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13017665530/npm-package-cloudflare-workers-shared-7378

@cloudflare/workflows-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13017665530/npm-package-cloudflare-workflows-shared-7378

Note that these links will no longer work once the GitHub Actions artifact expires.

---

[email protected] includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20250124.0
workerd	1.20250124.0	1.20250124.0
workerd --version	1.20250124.0	2025-01-24

Please ensure constraints are pinned, and miniflare/workerd minor versions match.

[gpanders]

The option is called "path-to-docker" but accepts a command (i.e. "docker") so maybe docker-cmd is a better name? Path implies a full path.

[IRCody]

This is used to find the binary for docker. So if it's on your $PATH you can use 'docker' but if not you can pass it here.

Maybe the description could be changed to something like:

Add the path to your docker binary if it's not on your $PATH?

[gpanders]

Can we make the default whatever the user is using (e.g. linux/arm64 on an M1 Mac and linux/amd64 on x86)?

[IRCody]

The reasoning for defaulting to linux/amd64 is that is the only supported platform in cc today.

[mikenomitch]

Yeah +1 to using amd64 as the default.

Shoudl we say in the description of build that it defaults to "architecture supported by Workers (linux/amd64)"?

[IRCody]

The default shows up in the help text:

...
--platform        platform to build for  [string] [default: "linux/amd64"]
...

We could add the extra text to the description I guess?