How?
We can bind-mount a binary from host on a docker guest with below in the Dockerfile.
mycontainer:
image: myimage
volumes:
- './path/on/docker/host:/path/inside/container'
#...
In a devcontainer.json file, above can be accomplished with below.
{
"name": "mycontainer",
"mounts": [
{
"source": "./path/on/docker/host",
"target": "/path/inside/container",
"type": "bind"
},
],
//...
}
In above fashion, we can bind application binaries as well. However, dynamically linked applications might not work as expected due to dependency errors in case the docker image does not have necessary shared libraries.
What?
The Terraform binary1 mounted as above works fine where the host OS is Ubuntu and the docker image runs Alpine Linux.
However, the Hugo binary2 does not work and fails with below error.
hugo: No such file or directory
Why?
This is expected since as evident from below output, the former binary is not a dynamic executable, while the latter is, according to the host’s ldd output.
╭ 19:53 [0s] [~]
╰─ ldd /usr/bin/terraform
not a dynamic executable
╭ 19:53 [0s] [~]
╰─ ldd /usr/bin/hugo
linux-vdso.so.1 (0x00007ffddc9cc000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007e4112358000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007e4112353000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007e4112000000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007e411226c000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007e4112267000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007e4112247000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007e4111c00000)
/lib64/ld-linux-x86-64.so.2 (0x00007e411237e000)