-
Notifications
You must be signed in to change notification settings - Fork 5.5k
move run
logic inside backend
#12908
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
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #12908 +/- ##
==========================================
- Coverage 53.39% 53.20% -0.20%
==========================================
Files 160 161 +1
Lines 16542 16696 +154
==========================================
+ Hits 8833 8883 +50
- Misses 6800 6898 +98
- Partials 909 915 +6 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
7af6eb8
to
3b848c3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
This MR contains the following updates: | Package | Update | Change | |---|---|---| | [docker/compose](https://github.com/docker/compose) | patch | `v2.37.1` -> `v2.37.2` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>docker/compose (docker/compose)</summary> ### [`v2.37.2`](https://github.com/docker/compose/releases/tag/v2.37.2) [Compare Source](docker/compose@v2.37.1...v2.37.2) #### What's Changed ##### ✨ Improvements - introduce `use_api_socket` by [@​ndeloof](https://github.com/ndeloof) in docker/compose#12908 ##### 🐛 Fixes - restore ContainerName in images --json by [@​ndeloof](https://github.com/ndeloof) in docker/compose#12943 - fix panic using w shortcut on project without watch support by [@​ndeloof](https://github.com/ndeloof) in docker/compose#12944 ##### 🔧 Internal - move `run` logic inside backend by [@​ndeloof](https://github.com/ndeloof) in docker/compose#12908 ##### ⚙️ Dependencies - bump compose-go to v2.6.5 by [@​ndeloof](https://github.com/ndeloof) in docker/compose#12958 - build(deps): bump github.com/containerd/containerd/v2 from 2.1.1 to 2.1.2 by [@​dependabot](https://github.com/dependabot) in docker/compose#12939 **Full Changelog**: docker/compose@v2.37.1...v2.37.2 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever MR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC42Mi4xIiwidXBkYXRlZEluVmVyIjoiNDAuNjIuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiUmVub3ZhdGUgQm90Il19-->
Apparently now We normally inject proxy variables into a build process and docker compose used to automatically used those. Now they are not even consumed, if explicitly supplied via |
Downgrading to |
@max-wittig I added an e2e test to check |
Thank you for your quick response! Maybe its relevant that we need to set
And maybe its actually another change in |
What I did
refactored
run
so that all the container management logic is owned by backendadded support for
use_api_socket
as a syntaxic sugar, adding bind/config resources to compose model, the same way it is implemented as experimental by docker/cli#5858 (waiting for actual support by Docker Engine)Related issue
(not mandatory) A picture of a cute animal, if possible in relation to what you did
