You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The recently released docker desktop 4.27.0 ships with the containerd backend storage feature in GA. When activating this feature, vagrant docker provider fails building vms from Dockerfile.
The log format docker build has changed with the new storage backend enabled. Vagrant fails to parse the built image id from the new log format.
Debug output
Bringing machine 'test' up with 'docker' provider...
==> test: Creating and configuring docker networks...
==> test: Building the container from a Dockerfile...
test: #0 building with "desktop-linux" instance using docker driver
test:
test: #1 [internal] load build definition from Dockerfile
test: #1 transferring dockerfile: 414B done
test: #1 DONE 0.0s
test:
test: #2 [internal] load metadata for docker.io/library/busybox:latest
test: #2 ...
test:
test: #3 [auth] library/busybox:pull token for docker-hub-remote.dr.corp.adobe.com
test: #3 DONE 0.0s
test:
test: #2 [internal] load metadata for docker.io/library/busybox:latest
test: #2 DONE 1.0s
test:
test: #4 [internal] load .dockerignore
test: #4 transferring context: 2B done
test: #4 DONE 0.0s
test:
test: #5 [1/1] FROM docker.io/library/busybox:latest@sha256:6d9ac9237a84afe1516540f40a0fafdc86859b2141954b4d643af7066d598b74
test: #5 resolve docker.io/library/busybox:latest@sha256:6d9ac9237a84afe1516540f40a0fafdc86859b2141954b4d643af7066d598b74 0.0s done
test: #5 CACHED
test:
test: #6 exporting to image
test: #6 exporting layers done
test: #6 exporting manifest sha256:c01f658213f7ce452a676d83e151941180c922ddddb7372d7ca656cab1febe37 done
test: #6 exporting config sha256:3e4fd538a9a0b729be05707cf805388be2fb701cfd5d44c6542f1988e8aef6e3 done
test: #6 exporting attestation manifest sha256:4655203e3ebfc7a5ba35a4b4810abbdeb2567a39e240433a8529dbbf3a95ed2c done
test: #6 exporting manifest list sha256:5ed6833079fe1dcc7b4c7573cd2dc73349e6a43d4c07e33250a8e9e8d07ac1d8 done
test: #6 naming to moby-dangling@sha256:5ed6833079fe1dcc7b4c7573cd2dc73349e6a43d4c07e33250a8e9e8d07ac1d8 done
test: #6 unpacking to moby-dangling@sha256:5ed6833079fe1dcc7b4c7573cd2dc73349e6a43d4c07e33250a8e9e8d07ac1d8 done
test: #6 DONE 0.0s
test:
test: View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/lw07gebd5hwfokvehf0kwhwxd
Vagrant received unknown output from `docker build` while building a container: #0 building with "desktop-linux" instance using docker driver
Expected behavior
vagrant docker vm is built and started.
Actual behavior
vagrant fails with Vagrant received unknown output from docker build while building a container
Reproduction information
Vagrant version
Vagrant 2.4.1
Host operating system
Mac OS 14.2.1
Docker for Mac 4.27.0 w/ containerd store activated
Guest operating system
N/A
Steps to reproduce
Install vagrant
Install docker desktop
activate Use containerd for pulling and storing images in docker desktop settings
vagrant up a vagrantfile using docker provider with a dockerfile
vagrant fails at the docker build step trying to parse image id from docker build output
The recently released docker desktop 4.27.0 ships with the containerd backend storage feature in GA. When activating this feature, vagrant docker provider fails building vms from Dockerfile.
The log format
docker build
has changed with the new storage backend enabled. Vagrant fails to parse the built image id from the new log format.Debug output
Expected behavior
vagrant docker vm is built and started.
Actual behavior
vagrant fails with
Vagrant received unknown output from
docker buildwhile building a container
Reproduction information
Vagrant version
Vagrant 2.4.1
Host operating system
Mac OS 14.2.1
Docker for Mac 4.27.0 w/ containerd store activated
Guest operating system
N/A
Steps to reproduce
Use containerd for pulling and storing images
in docker desktop settingsvagrant up
a vagrantfile using docker provider with a dockerfileVagrantfile
Dockerfile:
FROM busybox
The text was updated successfully, but these errors were encountered: