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 host Docker storage driver actually doesn't
matter at all because we use DinD. This was my
mistake.
Signed-off-by: Jacob Weinstock <[email protected]>
Copy file name to clipboardExpand all lines: README.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,8 +168,6 @@ For use cases where having container images already available in Docker is neede
168
168
169
169
> Note: This will increase the overall size of HookOS. As HookOS is an in memory OS, make sure that the size increase works for the machines you are provisioning.
170
170
171
-
> Note: Hook-docker uses the `overlay2` storage driver. For the `pull-images.sh` script to work, your local Docker storage driver must be `overlay2`.
172
-
173
171
1. Create a file named `images.txt` in the [images/hook-embedded/](images/hook-embedded/) directory.
174
172
1. Populate this `images.txt` file with the list of images to be embedded. See [images/hook-embedded/images.txt.example](images/hook-embedded/images.txt.example) for details on the required file format.
175
173
1. Change directories to [images/hook-embedded/](images/hook-embedded/) and run [`pull-images.sh`](images/hook-embedded/pull-images.sh) script when building amd64 images and run [`pull-images.sh arm64`](images/hook-embedded/pull-images.sh) when building arm64 images. Read the comments at the top of the script for more details.
0 commit comments