File _patchinfo of Package patchinfo.40458

<patchinfo incident="40458">
  <issue tracker="jsc" id="PED-8905"/>
  <issue tracker="jsc" id="PED-12534"/>
  <issue tracker="bnc" id="1247594">L3: docker-buildx packages for SLE 15 SP6/SP7 missing in release [thread::IOLoQg1mLmSVXmwVLvfYuis::]</issue>
  <packager>cyphar</packager>
  <rating>moderate</rating>
  <category>recommended</category>
  <summary>Recommended update for docker</summary>
  <description>This update for docker fixes the following issues:

Update to docker-buildx v0.28.0.

See upstream changelog: &lt;https://github.com/docker/buildx/releases/tag/v0.28.0&gt;

Update to Docker 28.4.0-ce:

See upstream changelog: &lt;https://docs.docker.com/engine/release-notes/28/#2840&gt;

- Update warnings and errors related to "docker buildx ..." so that they
  reference our openSUSE docker-buildx packages.

- Enable building docker-buildx for SLE15 systems with SUSEConnect secret
  injection enabled. PED-12534 PED-8905 bsc#1247594

  As docker-buildx does not support our SUSEConnect secret injection (and some
  users depend "docker build" working transparently), patch the docker CLI so
  that "docker build" will no longer automatically call "docker buildx build",
  effectively making DOCKER_BUILDKIT=0 the default configuration. Users can
  manually use "docker buildx ..." commands or set DOCKER_BUILDKIT=1 in order
  to opt-in to using docker-buildx.

  Users can silence the "docker build" warning by setting DOCKER_BUILDKIT=0
  explicitly.

  In order to inject SCC credentials with docker-buildx, users should use

    RUN --mount=type=secret,id=SCCcredentials zypper -n ...

  in their Dockerfiles, and

    docker buildx build --secret id=SCCcredentials,src=/etc/zypp/credentials.d/SCCcredentials,type=file .

  when doing their builds.
</description>
<message>Updating docker will restart the docker service, which may stop some of your docker containers. Do you want to proceed with the update?</message>
</patchinfo>