He said shared libraries, not shell libraries. And he’s bot saying you can run a native image in a computer with no OS. He means you can run it in a docker container whose image contains only the binary, and nothing more. This is because when you statically link shared libraries, they are built into the binary. So you don’t need a docker image with any library. You still need a kernel, because your app is going to make some sort of syscall. Try learning about how kernels, syscalls, containers and shared/static libraries works to understand better
In another TH-cam video by some other Oracle guy, there's a really nice explanation of this. That video is a technical discussion rather than a sales pitch for GraalVM EE version. Update: here's the video, it's well-worth the watch. th-cam.com/video/sI-zXYLKzfk/w-d-xo.html
1:24 - here the presenter mentions that statically linking shell libraries would enable your application to run without OS!!! how would that work?
He said shared libraries, not shell libraries.
And he’s bot saying you can run a native image in a computer with no OS. He means you can run it in a docker container whose image contains only the binary, and nothing more.
This is because when you statically link shared libraries, they are built into the binary. So you don’t need a docker image with any library.
You still need a kernel, because your app is going to make some sort of syscall.
Try learning about how kernels, syscalls, containers and shared/static libraries works to understand better
@@greyshopleskin2315 makes sense now, thanks
In another TH-cam video by some other Oracle guy, there's a really nice explanation of this.
That video is a technical discussion rather than a sales pitch for GraalVM EE version.
Update: here's the video, it's well-worth the watch. th-cam.com/video/sI-zXYLKzfk/w-d-xo.html