Error on building docker image

[jmellander]

I'm trying to build an image using vctl, but it seems I'm getting an error from the builder itself.

I run:

[username@hostname] [current directory] % vctl build -f /Users/[path masked]/Downloads/image-docker-64/Dockerfile -t [masked tag] /Users/[home of user]/.vctl/storage/

Password:

INFO building image [masked tag] with jobId 15dade5d-2184-411b-a696-bd97a37bcd25 using internal builder instance...

INFO preparing base images...                    

INFO done preparing cache for images: []         

INFO builder image vctl.local/vctl-builder:0.14.0 is ready

INFO preparing builder: vctl-builder-15dade5d    

INFO starting builder: vctl-builder-15dade5d     

INFO container vctl-builder-15dade5d started     

ERROR image build failed, please review above build logs for details

      if you are seeing 'no space left on device' error, retry 'vctl build' with the '--builder-mem' option to allocate more memory

[username@hostname] [current directory] %

When I look at containerd.log, it says:

time="2020-09-25T13:29:44.271869000+02:00" level=info msg="starting signal loop namespace=vctl-internal path=/Users/[masked path]/.vctl/storage/containerd/state/io.containerd.runtime.v2.task/vctl-internal/vctl-b" namespace=vctl pid=18995

time="2020-09-25T13:29:44.768813000+02:00" level=error msg="failed to find the container or sandbox cri annotations" module=libcrx package=ociruntimespec

time="2020-09-25T13:29:53.591203000+02:00" level=warning msg="container :vctl-builder-15dade5d does not have port mapping, ignore" module=libcrx package=ocicontainer

time="2020-09-25T13:29:53.599622000+02:00" level=info msg="shim disconnected" id=vctl-builder-15dade5d

time="2020-09-25T13:29:53.599685000+02:00" level=warning msg="cleaning up after shim disconnected" id=vctl-builder-15dade5d namespace=vctl-internal

time="2020-09-25T13:29:53.599702000+02:00" level=info msg="cleaning up dead shim"

To me it looks like it's the builder container itself that is struggling. What could I be doing wrong?

Any hint appreciated.

This is when using Fusion Pro 11.5.6.

[Mikero]

Hm... can we take a look at the Dockerfile?

[jmellander]

Mikero​ Certainly. Attached is the docker and docker-compose files. There are also two file system files, but I'm guessing these are not as relevant, and also too big to post here.

For running the image as a container, there is also a shell script which results in a command like below (with the variables replaced of course).

docker run  -itd $dk_memory $dk_env --name $dk_name $dk_portmap $dk_extra $dk_caps $dk_image

But if I interpret the logs correctly (and based on what I expect) vctl is not trying to run the image at this stage. (That would be a later step.)

Thanks
Jonas

[Mikero]

Thanks for that.

I see the same thing here.

While vctl doesn't yet support docker-compose, the `vctl build` should still work... As the error says, it looks like we're missing some annotation... I'll do some comparisons with some images I know work and see what the diff is.

[Guddler]

Is support for docker-compose on the roadmap?

I had no idea that vctl even existed until just after I'd converted my containers to use docker-compose :smileylaugh:

I'm going to test if they work individually with build today and whether it provides any benefit over just installing docker desktop.

[Mikero]

It's something we're looking at

[rbEoco8U]

Hello Michael

Is there any update on the issue? I get a similar error message when I try to build a docker image:

INFO[0075] Taking snapshot of files...                  
INFO[0075] ENTRYPOINT ["python", "src/detection/check_events.py"] 
INFO[0075] Generating final image file...               
INFO[0075] Finished generating final image file         
ERROR image build failed, please review above build logs for details
      if you are seeing 'no space left on device' error, retry 'vctl build' with the '--builder-mem' option to allocate more memory 

Looking at the containerd.log file, I get the same error as reported. Here are all log entries corresponding to the build run:

time="2021-01-20T13:01:48.699043000+01:00" level=info msg="starting signal loop namespace=vctl-internal path=$HOME/.vctl/storage/containerd/state/io.containerd.runtime.v2.task/vctl-internal/vctl-b" namespace=vctl pid=16497
time="2021-01-20T13:01:49.169904000+01:00" level=error msg="failed to find the container or sandbox cri annotations" module=libcrx package=ociruntimespec
time="2021-01-20T13:01:50.132696000+01:00" level=warning msg="container :vctl-builder-37335e71 does not have port mapping, ignore" module=libcrx package=ocicontainer
time="2021-01-20T13:03:05.920949000+01:00" level=warning msg="container :vctl-builder-37335e71 does not have port mapping, ignore" module=libcrx package=ocicontainer
time="2021-01-20T13:03:08.463902000+01:00" level=info msg="shim disconnected" id=vctl-builder-37335e71

I'm running VMware Fusion 12.1.0

I've attached the dockerfile, I used for the build.

It would be great to get this fixed. I really love the ability to do most of my docker builds with VMware instead of the Docker for Mac app. If it would work reliably and additionally support docker-compose, I finally could get rid of the Docker for Mac.

Best regards
Eric