feat(library): Introduce Java 17 as library

[razvand]

Introduce Java 17 image (ELF Loader) for bincompat runs.

Add Kraftfile to build for QMEU and Firecracker on x86_64 using initrd for volume support. The current build uses embedded initrd to build a single image consisting of both the kernel and the initial ramdisk.

Add GitHub workflow to build and deploy the image. Add success badge in README.md.

[Mihnea0Firoiu]

It fails to build rootfs:

<!> building rootfs                                                            x86_64 [0.0s]
 W  could not connect to BuildKit client, is BuildKit running?
 W  
 W  By default, KraftKit will look for a native install which
 W  is located at /run/buildkit/buildkit.sock.  Alternatively, you
 W  can run BuildKit in a container (recommended for macOS users)
 W  which you can do by running:
 W  
 W    docker run --rm -d --name buildkit --privileged moby/buildkit:latest
 W    export KRAFTKIT_BUILDKIT_HOST=docker-container://buildkit
 W  
 W  For more usage instructions visit: https://unikraft.org/buildkit
 W  
 E  could not get BuildKit info: failed to call info: Unavailable: connection error: desc = 
 E  could not get BuildKit info: failed to call info: Unavailable: connection error: desc = 

Am I doing something wrong? For another app from library, such as nginx, it works.

[Mihnea0Firoiu]

It fails to build rootfs:

<!> building rootfs                                                            x86_64 [0.0s]
 W  could not connect to BuildKit client, is BuildKit running?
 W  
 W  By default, KraftKit will look for a native install which
 W  is located at /run/buildkit/buildkit.sock.  Alternatively, you
 W  can run BuildKit in a container (recommended for macOS users)
 W  which you can do by running:
 W  
 W    docker run --rm -d --name buildkit --privileged moby/buildkit:latest
 W    export KRAFTKIT_BUILDKIT_HOST=docker-container://buildkit
 W  
 W  For more usage instructions visit: https://unikraft.org/buildkit
 W  
 E  could not get BuildKit info: failed to call info: Unavailable: connection error: desc = 
 E  could not get BuildKit info: failed to call info: Unavailable: connection error: desc = 

Am I doing something wrong? For another app from library, such as nginx, it works.

Fixed the issue, I just had to run BuildKit into a container, as is written above.

[StefanJum]

All good.
Reviewed-by: Stefan Jumarea stefanjumarea02@gmail.com

[Mihnea0Firoiu]

All good!
Reviewed-by: Mihnea Firoiu mihneafiroiu0@gmail.com

[StefanJum]

We can merge this, running the application fails with the issue described in #67

Reviewed-by: Stefan Jumarea stefanjumarea02@gmail.com
Approved-by: Stefan Jumarea stefanjumarea02@gmail.com

[StefanJum]

Reviewed-by: Stefan Jumarea stefanjumarea02@gmail.com
Approved-by: Stefan Jumarea stefanjumarea02@gmail.com