chore(deps): bump github.com/docker/docker from 25.0.5+incompatible to 26.1.4+incompatible #38
Conversation
This file contains 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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 4.5.1 to 4.5.3. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v4.5.3/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v4.5.3/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps and [ws](https://github.com/websockets/ws). These dependencies needed to be updated together. Updates `ws` from 6.2.2 to 8.17.1 - [Release notes](https://github.com/websockets/ws/releases) - [Commits](websockets/ws@6.2.2...8.17.1) Updates `ws` from 7.5.9 to 8.17.1 - [Release notes](https://github.com/websockets/ws/releases) - [Commits](websockets/ws@6.2.2...8.17.1) Updates `ws` from 8.16.0 to 8.17.1 - [Release notes](https://github.com/websockets/ws/releases) - [Commits](websockets/ws@6.2.2...8.17.1) Updates `ws` from 8.17.0 to 8.17.1 - [Release notes](https://github.com/websockets/ws/releases) - [Commits](websockets/ws@6.2.2...8.17.1) --- updated-dependencies: - dependency-name: ws dependency-type: indirect - dependency-name: ws dependency-type: indirect - dependency-name: ws dependency-type: indirect - dependency-name: ws dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Added an example on how they could be used as a simple integration test
Bumps [braces](https://github.com/micromatch/braces) from 3.0.2 to 3.0.3. - [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md) - [Commits](micromatch/braces@3.0.2...3.0.3) --- updated-dependencies: - dependency-name: braces dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
the kvstore will eventually become the autoscaler so might as well create it as a cli app
docker driver breaks kube-proxy for new clusters, used to stop the clusters for kube-proxy to avoid CrashLoopBackOff error. using kvm2 fixed it.
We want to allow the clusters to be reached by the client and with each other, since by design mnikube runs each cluster in a private subnets when using kvm driver, simply adding routes using route command does not work, also tried port-forwarding in the host and sending requests within the vm to the host and it didn't work, and to fix it this you need to manually edit the network settings from outside and destroy it and restart the vm as explained here kubernetes/minikube#11499, which makes the tests harder to run. A solution would be to use docker and create a loop until all kube-proxy pods are running as needed, but it can only do 2 clusters for some reason, the third will automatically use kvm2. moreover it behaves differently for each run. But that won't be needed as virtualbox driver runs all clusters within the same network. Also registered 3 different providers, one for each cluster using their own ipfs node. and simplified the scripts.
Images were pulled from remote registries and not from the already saved images from ipfs during pod creation. so i tried to tag the images with the CID and replace the image url with the tag. this also fixes the case where the client uploads from private registries, because they will be inaccessible such as the case with the autoscaler in the test that is stored in the local docker registry. The problem was that containerd will always prefix the tagged images with docker.io/ to resolve them remotely again, therefore bypassing the saved images from ipfs. and unless its a known registry, such as gcr or docker.io, it will always get prefixed, even localhost. So the solution was simple,just disable pulling images completely, therefore it will resort to the saved images with prefixing, it just takes it as it is.
Needed to pass the provider keys dynamically, and templating wont work with helmfile without a proper helm chart, because it won't subsitute the values therefore produce incorrect yaml.
The client selects any instance and provide it with all the apocryph node gateways and it will trigger the rest and for the cluster instead of sending multiple connect requests to every provider.
…-4.5.3 chore(deps-dev): bump vite from 4.5.1 to 4.5.3
…i-e39ca5aae1 chore(deps): bump ws
….com/rs/cors-1.11.0 chore(deps): bump github.com/rs/cors from 1.9.0 to 1.11.0
…es-3.0.3 chore(deps): bump braces from 3.0.2 to 3.0.3
Bumps [github.com/docker/docker](https://github.com/docker/docker) from 25.0.5+incompatible to 26.1.4+incompatible. - [Release notes](https://github.com/docker/docker/releases) - [Commits](moby/moby@v25.0.5...v26.1.4) --- updated-dependencies: - dependency-name: github.com/docker/docker dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
|
Superseded by #40. |
dependabot
bot
deleted the
dependabot/go_modules/github.com/docker/docker-26.1.4incompatible
branch
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.
Bumps github.com/docker/docker from 25.0.5+incompatible to 26.1.4+incompatible.
Release notes
Sourced from github.com/docker/docker's releases.
... (truncated)
Commits
de5c9cfMerge pull request #47912 from thaJeztah/26.1_backport_vendor_containerd_1.7.18c62dcf8Merge pull request #47911 from thaJeztah/26.1_backport_bump_containerd_binary...17315a2vendor: github.com/containerd/containerd v1.7.18cbd9418update containerd binary to v1.7.18fb9f72aMerge pull request #47904 from thaJeztah/26.1_backport_bump_go1.21.113115daaupdate to go1.21.112861734Merge pull request #47892 from thaJeztah/26.1_backport_api_docs_network_confi...9c95aeaMerge pull request #47893 from thaJeztah/26.1_backport_bump_docker_py3e09e19Merge pull request #47894 from thaJeztah/26.1_backport_vendor_containerd_v1.7.1765b679aMerge pull request #47889 from thaJeztah/26.1_backport_platforms_err_handlingDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.