Skip to content

dagger: use existing dagger engine if any #149

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

dagger: use existing dagger engine if any #149

wants to merge 1 commit into from

Conversation

@tiborvass
Copy link
Collaborator

Fixes #148

kpenfound
kpenfound approved these changes Jun 30, 2025
View reviewed changes
Copy link
Contributor

@kpenfound kpenfound left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ship it! to confirm my answer to @marcosnils 's question: its ok if the cu mcp is running on a different engine than cu terminal?

@tiborvass tiborvass marked this pull request as draft June 30, 2025 16:32
@marcosnils
Copy link

Fixes #148

as discussed in Discord, it doesn't address #148 directly as there's still going to be a struggle between the cu and the dagger binary re-provisioning engines every time they're called independently of the cu terminal sub-command.

@marcosnils
Copy link

@aluzzardi this has been moved to draft per my last comment 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@aluzzardi aluzzardi aluzzardi approved these changes

@kpenfound kpenfound kpenfound approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Engine version conflicts between cu and dagger.

4 participants

@tiborvass @marcosnils @aluzzardi @kpenfound