When I run docker version, I will see docker-init version in the Server part. May I ask what is docker-init for? Is it a Linux init system specific to Docker Desktop? I couldn't find any information about it.
It shows what version of Tini is included in the version of Docker you have installed.
The project page tells what it does better than I can.
Related
I have docker-compose 1.25.4 on a system, and docker 19.03. How do I know which version of Compose file format it supports, without trying a bunch or searching through release notes etc?
I determined by trial and error that the highest Compose file format version that docker-compose 1.25.4 supports is 3.7. Therefore, my docker-compose.yml requires version: "3.7".
But what if I need to determine this programmatically? Or reliably, without trial and error, and without looking at release notes?
The docs at https://docs.docker.com/compose/compose-file/compose-versioning/ suggest that highest version should be 3.8 but this does not work. Indeed the release notes indicate that 3.8 became supported as of docker-compose 1.25.5.
I looked through various docker-compose commands and could not spot anything that would say "This version of docker-compose supports Compose file version up to x.y".
I figured out that there is no way to find this out via the cli.
You need to check the docker-compose github releases for this.
For example on Ubuntu: v1.25.0 version of docker-compose which is currently the latest and gets to be installed by default, but it is compatible with the 3.7 at highest.
https://github.com/docker/compose/releases/tag/1.25.0
The Compose file format compatibility matrix part is the interesting here.
I installed Docker on a Red Hat Enterprise Linux Server 7.5 (Maipo) system:
docker version
Version: 1.13.1
API version: 1.26
Package version: docker-1.13.1-58.git87f2fab.e17.x86_64
OS/Arch: linux/amd64
Now if I try to run a docker image, I get errors similar to this:
docker run docker.io/jupyter/datascience-notebook
tini: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
I have searched for help and have already taken a multitude of possible actions:
libraries seem to be linked correctly
all libraries are up to date
Hello-World example works
I also came across information saying that running containers from docker.io / hub.docker.com under RHEL is not supported - which I don't really get, as main purpose of docker is to enable running programs independent from their OS...?
https://access.redhat.com/solutions/1408853 Does this mean using docker under RHEL does not really provide me with the possibility of easily deploying/sharing a docker-image with non-RHEL users?
Also, does this mean I can only access and use official RHEL-docker images?
https://access.redhat.com/containers/?start=90#/search/
As I wanted to use docker to have ready-to-go environments with R-Python/Jupyter/H2o (and similar), I'm disappointed because I could not find suitable images for RHEL there.
So, my questions would be:
Is it possible to run docker.io / hub.docker.com images under RHEL7.5?
if not, could I share my own created docker images under RHEL7.5 to other users with different OS versions?
Are there other projects / sites to share docker-images for data science purposes on RHEL?
Would you agree that my next step would be: building my own docker-image, adding R/Python/jupyter step by step?
Best regards,
workah0lic
This error message
tini: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
comes from within the container image. It could be a corrupted container image, but the message is also printed when the glibc dynamic linker determines that the kernel features are not sufficient for loading libc.so.6. I looked at the image (digest is sha256:79f929bd0e58fa9cb238dceda48b0c8360e748d09b476b429216c93dac0bd783), and it appears to require kernel 3.2, so the Red Hat Enterprise Linux 7 kernel version of 3.10 should be sufficient.
In fact, I cannot reproduce this problem with kernel-3.10.0-862.6.3.el7.x86_64 and docker-1.13.1-58.git87f2fab.el7.x86_64. You could try to run this command to obtain additional information about dynamic linker behavior:
docker run -e LD_DEBUG=all docker.io/jupyter/datascience-notebook
I installed virtualbox 5.2 from their website. And I ran this command..
docker-machine create -d virtualbox dev
then I got this..
Running pre-create checks...
Error with pre-create check: "We support Virtualbox starting with version 5. Your VirtualBox install is
"WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.14.3-300.fc27.x86_64) or it failed to
load. Please recompile the kernel module and install it by
sudo /sbin/vboxconfig
You will not be able to start VMs until this problem is fixed.\\n5.2.2r119230\".
Please upgrade at https://www.virtualbox.org"
I did as it suggested..
sudo /sbin/vboxconfig
then..
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
kernel-devel kernel-devel-4.14.3-300.fc27.x86_64
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
kernel-devel kernel-devel-4.14.3-300.fc27.x86_64
..and I don't understand anymore. Please help.
Install the kernel-devel package and it will continue. Btw, this is not a programming question, there are better forums for such questions...
I am having the following warning message when issueing docker commands: (ex: docker ps)
C:\Users\whha>docker ps
time="2017-01-24T23:17:36+01:00" level=warning msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
Any idea how can it be avoided?
I´m running docker using docker toolbox on windows 8.1.
Installing the last available version solved the problem for me (https://github.com/docker/toolbox/releases) :
BEFORE
minux#DESKTOP-OCQQ65T MINGW64 /c
$ docker --version
time="2017-04-05T17:56:55+02:00" level=info msg="Unable to use system
certificate pool: crypto/x509: system root pool is not available on Windows"
Docker version 17.03.1-ce, build c6d412e
AFTER
minux#DESKTOP-OCQQ65T MINGW64 /c
$ docker --version
Docker version 17.04.0-ce-rc2, build 2f35d73
I started having this problem today after updating to the docker toolbox version 1.13.1 of Docker Toolbox for windows.
Checking around the internet, and saw a github issue that this problem can't be fixed for windows.
https://github.com/docker/for-win/issues/422
Hence, probably has to follow #mayur_patil's suggestion to roll back to 1.12.x version. FYI, previous release can be found here: https://github.com/docker/toolbox/releases
I have installed docker toolbox version 1.13.1 for windows.
OS : Windows 10 Enterprise.
I solved the same issue with the v 1.12.6 instead 1.13.x.
You can change version series.
I was getting this error on Docker-toolbox 1.13.1
After that I downgraded to 1.12.2 and my problem solved.
OS: Windows 7 SP1
Check out and reply.
Had the same problem and solved it by download v1.12.6 from:
https://github.com/docker/toolbox/releases
I just installed docker and boot2docker on Mavericks. I did the usual
boot2docker init
boot2docker start
export DOCKER_HOST=tcp://localhost:4243
and it says the server is up and running. But when I try to connect (e.g. docker info) I get
2014/06/07 10:45:55 Get http://localhost:4243/v1.11/info: EOF
I'm guessing something is wrong with the daemon but I can't crack this one... Does anyone know what it could be?
Note: I didn't install the bundled copy of VirtualBox when I installed docker/boot2docker because I already had it installed. Could there be something missing from that?
https://github.com/boot2docker/boot2docker/releases/tag/v0.12.0
Note: this update changes the exposed Docker port from 4243 to 2375,
and will require the v0.12.0 version of the new boot2docker management tool.
This Boot2Docker release is not backwards compatible with older management tools
I have the same problem, but couldn't really use boot2docker v0.12.0 yet.
I just install boot2docker using Go directly go get github.com/boot2docker/boot2docker-cli