Skip to content

Conversation

@pull
Copy link

@pull pull bot commented May 10, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.1)

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added the ⤵️ pull label May 10, 2025
dependabot bot and others added 29 commits September 9, 2025 22:02
Bumps the golang-x group with 2 updates in the / directory: [golang.org/x/crypto](https://github.com/golang/crypto) and [golang.org/x/net](https://github.com/golang/net).


Updates `golang.org/x/crypto` from 0.41.0 to 0.42.0
- [Commits](golang/crypto@v0.41.0...v0.42.0)

Updates `golang.org/x/net` from 0.43.0 to 0.44.0
- [Commits](golang/net@v0.43.0...v0.44.0)

Updates `golang.org/x/sync` from 0.16.0 to 0.17.0
- [Commits](golang/sync@v0.16.0...v0.17.0)

Updates `golang.org/x/sys` from 0.35.0 to 0.36.0
- [Commits](golang/sys@v0.35.0...v0.36.0)

Updates `golang.org/x/term` from 0.34.0 to 0.35.0
- [Commits](golang/term@v0.34.0...v0.35.0)

Updates `golang.org/x/text` from 0.28.0 to 0.29.0
- [Release notes](https://github.com/golang/text/releases)
- [Commits](golang/text@v0.28.0...v0.29.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  dependency-version: 0.42.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: golang-x
- dependency-name: golang.org/x/net
  dependency-version: 0.44.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: golang-x
- dependency-name: golang.org/x/sync
  dependency-version: 0.17.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: golang-x
- dependency-name: golang.org/x/sys
  dependency-version: 0.36.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: golang-x
- dependency-name: golang.org/x/term
  dependency-version: 0.35.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: golang-x
- dependency-name: golang.org/x/text
  dependency-version: 0.29.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: golang-x
...

Signed-off-by: dependabot[bot] <support@github.com>
- move blkio code to a separate file
- return block device paths instead of major:minor numbers
- update blkio device tests to use blk devices in place of char devices

Signed-off-by: Swapnanil-Gupta <swpnlg@amazon.com>
…/xx-1.7.0

build(deps): bump tonistiigi/xx from 1.6.1 to 1.7.0
…-x-f5ce813bf4

build(deps): bump the golang-x group across 1 directory with 6 updates
….com/compose-spec/compose-go/v2-2.8.2

build(deps): bump github.com/compose-spec/compose-go/v2 from 2.8.1 to 2.8.2
Signed-off-by: ningmingxiao <ning.mingxiao@zte.com.cn>
The behavior of CPU shares was changed intentionally in runc v1.4.0-rc.1.

See runc PR 4896

Fix 4519

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
fix: return block device paths instead of major:minor numbers in `container inspect`
Fix `TestRunCgroupV2` with runc v1.4.0-rc.1
Bumps [github.com/containerd/nydus-snapshotter](https://github.com/containerd/nydus-snapshotter) from 0.15.2 to 0.15.4.
- [Release notes](https://github.com/containerd/nydus-snapshotter/releases)
- [Commits](containerd/nydus-snapshotter@v0.15.2...v0.15.4)

---
updated-dependencies:
- dependency-name: github.com/containerd/nydus-snapshotter
  dependency-version: 0.15.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
….com/containerd/nydus-snapshotter-0.15.4

build(deps): bump github.com/containerd/nydus-snapshotter from 0.15.2 to 0.15.4
Signed-off-by: Arjun Raja Yogidas <arjunry@amazon.com>
Bumps [github.com/compose-spec/compose-go/v2](https://github.com/compose-spec/compose-go) from 2.8.2 to 2.9.0.
- [Release notes](https://github.com/compose-spec/compose-go/releases)
- [Commits](compose-spec/compose-go@v2.8.2...v2.9.0)

---
updated-dependencies:
- dependency-name: github.com/compose-spec/compose-go/v2
  dependency-version: 2.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
….com/compose-spec/compose-go/v2-2.9.0

build(deps): bump github.com/compose-spec/compose-go/v2 from 2.8.2 to 2.9.0
Bumps [actions/cache](https://github.com/actions/cache) from 4.2.4 to 4.3.0.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@0400d5f...0057852)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-version: 4.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
fix:forbid to restart/start container created by k8s
…tions/cache-4.3.0

build(deps): bump actions/cache from 4.2.4 to 4.3.0
When running in rootful mode, reserve the ports on the host
so that the ports appears on /proc/net/tcp.

This also prevents other processes from binding to the same ports.

Note that in rootless mode this is not necessary because
RootlessKit's port driver already reserves the ports.

See lima-vm/lima issue 4085

Similar patterns are used in Docker and Podman.
- moby/moby PR 48132
- containers/podman PR 23446

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
rootful: reserve the ports on the host
Bumps [docker/login-action](https://github.com/docker/login-action) from 3.5.0 to 3.6.0.
- [Release notes](https://github.com/docker/login-action/releases)
- [Commits](docker/login-action@184bdaa...5e57cd1)

---
updated-dependencies:
- dependency-name: docker/login-action
  dependency-version: 3.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
…cker/login-action-3.6.0

build(deps): bump docker/login-action from 3.5.0 to 3.6.0
TestReservePorts tests that a published port appears
as a listening port on the host.

Follow-up to PR 4526

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Bumps the docker group with 2 updates: [github.com/docker/cli](https://github.com/docker/cli) and [github.com/docker/docker](https://github.com/docker/docker).


Updates `github.com/docker/cli` from 28.4.0+incompatible to 28.5.0+incompatible
- [Commits](docker/cli@v28.4.0...v28.5.0)

Updates `github.com/docker/docker` from 28.4.0+incompatible to 28.5.0+incompatible
- [Release notes](https://github.com/docker/docker/releases)
- [Commits](moby/moby@v28.4.0...v28.5.0)

---
updated-dependencies:
- dependency-name: github.com/docker/cli
  dependency-version: 28.5.0+incompatible
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: docker
- dependency-name: github.com/docker/docker
  dependency-version: 28.5.0+incompatible
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: docker
...

Signed-off-by: dependabot[bot] <support@github.com>
…-a96ddb1be1

build(deps): bump the docker group with 2 updates
AkihiroSuda and others added 30 commits December 16, 2025 11:47
test: refactor compose_up_linux_test.go to use Tigron
Default net.ipv4.ip_unprivileged_port_start to 0 inside containers
Fix ambiguous flag in command reference for `nerdctl image prune`: `-f` was given as the short flag for both `--filter` and `--force`, but checking the source this should be `--force` only.

Signed-off-by: Kristoffer Grönlund <k@ziran.se>
nerdctl image prune -f means --force, not --filter
Fix issue 4664

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Fix `'C:\\Program Files\\Linux Containers\\kernel' not found`
Bumps [github.com/containerd/containerd/v2](https://github.com/containerd/containerd) from 2.2.0 to 2.2.1.
- [Release notes](https://github.com/containerd/containerd/releases)
- [Changelog](https://github.com/containerd/containerd/blob/main/RELEASES.md)
- [Commits](containerd/containerd@v2.2.0...v2.2.1)

---
updated-dependencies:
- dependency-name: github.com/containerd/containerd/v2
  dependency-version: 2.2.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Bumps [github.com/containerd/nydus-snapshotter](https://github.com/containerd/nydus-snapshotter) from 0.15.9 to 0.15.10.
- [Release notes](https://github.com/containerd/nydus-snapshotter/releases)
- [Commits](containerd/nydus-snapshotter@v0.15.9...v0.15.10)

---
updated-dependencies:
- dependency-name: github.com/containerd/nydus-snapshotter
  dependency-version: 0.15.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [github.com/rootless-containers/rootlesskit/v2](https://github.com/rootless-containers/rootlesskit) from 2.3.5 to 2.3.6.
- [Release notes](https://github.com/rootless-containers/rootlesskit/releases)
- [Commits](rootless-containers/rootlesskit@v2.3.5...v2.3.6)

---
updated-dependencies:
- dependency-name: github.com/rootless-containers/rootlesskit/v2
  dependency-version: 2.3.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
….com/containerd/nydus-snapshotter-0.15.10

build(deps): bump github.com/containerd/nydus-snapshotter from 0.15.9 to 0.15.10
….com/containerd/containerd/v2-2.2.1

build(deps): bump github.com/containerd/containerd/v2 from 2.2.0 to 2.2.1
….com/rootless-containers/rootlesskit/v2-2.3.6

build(deps): bump github.com/rootless-containers/rootlesskit/v2 from 2.3.5 to 2.3.6
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 3.11.1 to 3.12.0.
- [Release notes](https://github.com/docker/setup-buildx-action/releases)
- [Commits](docker/setup-buildx-action@e468171...8d2750c)

---
updated-dependencies:
- dependency-name: docker/setup-buildx-action
  dependency-version: 3.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/attest-build-provenance](https://github.com/actions/attest-build-provenance) from 3.0.0 to 3.1.0.
- [Release notes](https://github.com/actions/attest-build-provenance/releases)
- [Changelog](https://github.com/actions/attest-build-provenance/blob/main/RELEASE.md)
- [Commits](actions/attest-build-provenance@977bb37...00014ed)

---
updated-dependencies:
- dependency-name: actions/attest-build-provenance
  dependency-version: 3.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
update containerd (2.2.1), runc (1.4.0), CNI plugins (1.9.0), BuildKit (0.26.3), imgcrypt (2.0.2), RootlessKit (2.3.6), etc.
…tions/attest-build-provenance-3.1.0

build(deps): bump actions/attest-build-provenance from 3.0.0 to 3.1.0
…cker/setup-buildx-action-3.12.0

build(deps): bump docker/setup-buildx-action from 3.11.1 to 3.12.0
When executing the command on a compose file like the one below, orphaned
containers are displayed, but the current implementation does not show
the IDs of these orphaned containers, making them difficult to identify.

```
$ cat compose-full.yaml
services:
  test:
    image: docker.io/library/busybox:latest
    command: ["sleep", "infinity"]
  orphan:
    image: docker.io/library/busybox:latest
    command: ["sleep", "infinity"]

$ cat compose-orphan.yaml
services:
  test:
    image: docker.io/library/busybox:latest
    command: ["sleep", "infinity"]

$ sudo nerdctl compose -f compose-full.yaml up -d
...

$ sudo nerdctl compose -f compose-orphan.yaml down -v
...
WARN[0010] found 1 orphaned containers: [0x4000340000], you can run this command with the --remove-orphans flag to clean it up
...
```

Therefore, this commit modifies to display the IDs of orphaned containers.

Additionally, since there was other logic that performed similar displays,
this commit also modifies it in the same manner.

Signed-off-by: Hayato Kiwata <haytok@amazon.co.jp>
…ed-containers

chore: improve the visibility of orphaned containers in logs
Refactor image management to use transfer service
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.