Skip to content
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.

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

fix: using the CLI+KurtosisCloud should not rely on the local Docker engine running #1726

Merged
merged 3 commits into from
Nov 9, 2023

Conversation

leoporoli
Copy link
Contributor

Description:

fix using the CLI+KurtosisCloud should not rely on the local Docker engine running

Is this change user facing?

YES

References (if applicable):

Fix #1719

@leoporoli leoporoli requested a review from h4ck3rk3y November 8, 2023 21:07
@leoporoli leoporoli added this pull request to the merge queue Nov 9, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 9, 2023
@leoporoli leoporoli added this pull request to the merge queue Nov 9, 2023
Merged via the queue into main with commit b447196 Nov 9, 2023
12 checks passed
@leoporoli leoporoli deleted the lporoli/ticket-1719 branch November 9, 2023 12:25
github-merge-queue bot pushed a commit that referenced this pull request Nov 9, 2023
🤖 I have created a release *beep* *boop*
---


##
[0.85.9](0.85.8...0.85.9)
(2023-11-09)


### Bug Fixes

* using the CLI+KurtosisCloud should not rely on the local Docker engine
running ([#1726](#1726))
([b447196](b447196)),
closes [#1719](#1719)

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: kurtosisbot <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

using the CLI+KurtosisCloud should not rely on local Docker engine running
2 participants