Commits on Jul 30, 2025

1. fix: Use Docker SDK to configure port binding (#526) …

   #### Summary
   
   While testing cloudquery/cloudquery#21179 I noticed syncing with docker plugins stopped working (even before cloudquery/cloudquery#21179).
   
   Looks like the host port is not mapped correctly (probably due to changes with recent docker engines), so the CLI can't connect to the plugin gRPC server.
   
   This PR fixes the issue by using the Docker SDK to get the port binding from a string value, ensuring the mapping is done correctly (hopefully for future versions as well)
   
   ---

   

   erezrokah authored Jul 30, 2025
   Configuration menu

   • View commit details
   • Copy full SHA for 63023a1
   • Browse repository at this point

   Copy the full SHA

   63023a1 View commit details

   Browse the repository at this point in the history

2. fix(deps): Update module github.com/docker/docker to v28.3.3+incompat… …

   …ible [SECURITY] (#528)
   
   This PR contains the following updates:
   
   | Package | Type | Update | Change |
   |---|---|---|---|
   | [github.com/docker/docker](https://redirect.github.com/docker/docker) | require | patch | `v28.3.2+incompatible` -> `v28.3.3+incompatible` |
   
   ### GitHub Vulnerability Alerts
   
   #### [CVE-2025-54388](https://redirect.github.com/moby/moby/security/advisories/GHSA-x4rx-4gw3-53p4)
   
   Moby is an open source container framework developed by Docker Inc. that is distributed as Docker Engine, Mirantis Container Runtime, and various other downstream projects/products. The Moby daemon component (dockerd), which is developed as [moby/moby](https://redirect.github.com/moby/moby) is commonly referred to as Docker, or Docker Engine.
   
   Firewalld is a daemon used by some Linux distributions to provide a dynamically managed firewall. When Firewalld is running, Docker uses its iptables backend to create rules, including rules to isolate containers in one bridge network from containers in other bridge networks.
   
   ### Impact
   
   The iptables rules created by Docker are removed when firewalld is reloaded using, for example "firewall-cmd --reload", "killall -HUP firewalld", or "systemctl reload firewalld".
   
   When that happens, Docker must re-create the rules. However, in affected versions of Docker, the iptables rules that prevent packets arriving on a host interface from reaching container addresses are not re-created.
   
   Once these rules have been removed, a remote host configured with a route to a Docker bridge network can access published ports, even when those ports were only published to a loopback address. Unpublished ports remain inaccessible.
   
   For example, following a firewalld reload on a Docker host with address `192.168.0.10` and a bridge network with subnet `172.17.0.0/16`, running the following command on another host in the local network will give it access to published ports on container addresses in that network: `ip route add 172.17.0.0/16 via 192.168.0.10`.
   
   Containers running in networks created with `--internal` or equivalent have no access to other networks. Containers that are only connected to these networks remain isolated after a firewalld reload.
   
   Where Docker Engine is not running in the host's network namespace, it is unaffected. Including, for example, Rootless Mode, and Docker Desktop.
   
   ### Patches
   
   Moby releases older than 28.2.0 are not affected. A fix is available in moby release 28.3.3.
   
   ### Workarounds
   After reloading firewalld, either:
   - Restart the docker daemon,
   - Re-create bridge networks, or
   - Use rootless mode.
   
   ### References
   https://firewalld.org/
   https://firewalld.org/documentation/howto/reload-firewalld.html
   
   ---
   
   ### Release Notes
   
   <details>
   <summary>docker/docker (github.com/docker/docker)</summary>
   
   ### [`v28.3.3+incompatible`](https://redirect.github.com/docker/docker/compare/v28.3.2...v28.3.3)
   
   [Compare Source](https://redirect.github.com/docker/docker/compare/v28.3.2...v28.3.3)
   
   </details>
   
   ---
   
   ### Configuration
   
   📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
   
   🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
   
   ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
   
   🔕 **Ignore**: Close this PR and you won't be reminded about this update again.
   
   ---
   
    - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
   
   ---
   
   This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate).
   <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC4yMi4xIiwidXBkYXRlZEluVmVyIjoiNDAuMjIuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiYXV0b21lcmdlIiwic2VjdXJpdHkiXX0=-->

   

   cq-bot authored Jul 30, 2025
   Configuration menu

   • View commit details
   • Copy full SHA for bcf436e
   • Browse repository at this point

   Copy the full SHA

   bcf436e View commit details

   Browse the repository at this point in the history

3. chore(main): Release v1.26.18 (#527) …

   🤖 I have created a release *beep* *boop*
   ---
   
   
   ## [1.26.18](v1.26.17...v1.26.18) (2025-07-30)
   
   
   ### Bug Fixes
   
   * **deps:** Update module github.com/docker/docker to v28.3.3+incompatible [SECURITY] ([#528](#528)) ([bcf436e](bcf436e))
   * Use Docker SDK to configure  port binding ([#526](#526)) ([63023a1](63023a1))
   
   ---
   This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).

   

   cq-bot authored Jul 30, 2025
   Configuration menu

   • View commit details
   • Copy full SHA for 9df3d95
   • Browse repository at this point

   Copy the full SHA

   9df3d95 View commit details

   Browse the repository at this point in the history