docs: use cosl binary in K8s tutorial charm to work around error#2232
Merged
dwilding merged 1 commit intocanonical:mainfrom Dec 12, 2025
Merged
docs: use cosl binary in K8s tutorial charm to work around error#2232dwilding merged 1 commit intocanonical:mainfrom
dwilding merged 1 commit intocanonical:mainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR implements a temporary workaround for build errors encountered when packing charms with cos-lite dependencies. Instead of installing cargo to build Rust dependencies from source, the charm now uses pre-built binary packages for cosl.
Key changes:
- Replaced the cargo build-package approach with charm-binary-python-packages configuration
- Updated documentation to explain the workaround and note it's temporary until the tutorial is modernized
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| examples/k8s-5-observe/charmcraft.yaml | Replaced cargo build-packages with charm-binary-python-packages configuration to use cosl binary |
| docs/tutorial/from-zero-to-hero-write-your-first-kubernetes-charm/observe-your-charm-with-cos-lite.md | Updated documentation to reflect the workaround approach and clarify the temporary nature of the fix |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
tonyandrewmeyer
approved these changes
Dec 12, 2025
Collaborator
tonyandrewmeyer
left a comment
There was a problem hiding this comment.
Thanks for sorting this out - I agree that temporarily making this change until we're ready to do the larger one is a good move.
james-garner-canonical
approved these changes
Dec 12, 2025
dwilding
added a commit
that referenced
this pull request
Dec 17, 2025
…e charms (#2233) As James suggested in #2229, this PR adds a scheduled workflow that packs and runs integration tests for our example charms. I've scheduled it to run each Tuesday before NZ hours. (We already have a workflow that lints and runs unit tests for the example charms. That workflow is fast and runs on PRs.) I've organised the example charms into three jobs: - The machine tutorial charm, based on a Charmcraft 4 profile. - The httpbin-demo K8s charm, based on a Charmcraft 4 profile. - The K8s tutorial charms, not based on a Charmcraft 4 profile. We're planning to refactor these later in the 26.04 cycle. I tested the jobs by temporarily enabling them for this PR. All are passing after #2232 merged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR temporarily fixes #2229. As a more permanent fix, we should switch the K8s tutorial to use the latest uv-based Charmcraft profiles. We're planning to do that later in the 26.04 cycle.