Don't connect to BuildKit daemon in test #4

Merged
lucas merged 1 commit from fix/check into master 2025-11-17 10:53:07 +01:00
Owner

The container spawned from the newly built image might not be running on
a Docker-in-Docker host that has access to a BuildKit daemon, so
attempting to use one is likely going to fail.
Merely checking that the CLI is installed will have to suffice.

The container spawned from the newly built image might not be running on a Docker-in-Docker host that has access to a BuildKit daemon, so attempting to use one is likely going to fail. Merely checking that the CLI is installed will have to suffice.
Don't connect to BuildKit daemon in test
All checks were successful
/ check (pull_request) Successful in 12s
c4f3843571
The container spawned from the newly built image might not be running on
a Docker-in-Docker host that has access to a BuildKit daemon, so
attempting to use one is likely going to fail.
Merely checking that the CLI is installed will have to suffice.
lucas scheduled this pull request to auto merge when all checks succeed 2025-11-17 10:52:43 +01:00
lucas merged commit f23e98e354 into master 2025-11-17 10:53:07 +01:00
lucas deleted branch fix/check 2025-11-17 10:53:07 +01:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lucas/forgejo-actions-buildkit-image!4
No description provided.