Trying to follow the tutorial "Using TensorFlow Serving via Docker": https://tensorflow.github.io/serving/docker
I'm getting the error below:
$ docker build --pull -t $USER/tensorflow-serving-devel -f Dockerfile.devel .
ERRO[1791] Can't add file /Users/bone/.docker/machine/machines/testD/disk.vmdk to tar: archive/tar: write too long
Sending build context to Docker daemon 194.3 GB
Error response from daemon: Untar re-exec error: exit status 1: output: write /.docker/machine/machines/default/disk.vmdk: no space left on device
The mistake was running this command on the command line outside the docker machine. Once this command was run inside the docker machine, it worked fine.
Related
I want to install and use docker on Server 2016 without docker dekstop(not supported). I am getting this error.
PS C:\Users\Administrator> docker run -t -i mcr.microsoft.com/windows/nanoserver:1809
Unable to find image 'mcr.microsoft.com/windows/nanoserver:1809' locally
1809: Pulling from windows/nanoserver
e2d245a3ce95: Extracting
[==================================================>] 103.3 MB/103.3 MB
C:\Program Files\docker\docker.exe: failed to register layer: re-exec
error: exit status 1: output: ProcessUtilityVMImage C:\ProgramData\docker\windowsfilter\a579423b585e834a4d02960cf2a96cccd4b69b4bfab7811774de7a83ad168729\UtilityVM:
The system cannot find the path specified..
See 'C:\Program Files\docker\docker.exe run --help'.
Thanks in advance for your help.
I was unable to install windowsServerCore container image with previous commands and then I entered the command: "docker run -t -i mcr.microsoft.com/windows/nanoserver:1809" to reach to offical page.
I am using,
Windows 10
Packer version : 1.8.4
Docker version 20.10.21, build baeda1f
When using any base image to build another docker image in packer using "packer build " command , the command aways gets hung in "docker run stage" , the logs are provided below :
$ packer build spark2223.prk.json
docker: output will be in this color.
==> docker: Creating a temporary directory for sharing data...
==> docker: Starting docker container...
docker: Run command: docker run -v C:\Users\mwandre\AppData\Roaming\packer.d\tmp2854382545:/packer-files -d -i -t --entrypoint=/bin/sh -- openjdk:8-jre-alpine
I am not sure how suddenly this problem started happening in my machine , untill yesterday it was working properly .
Any help would be apreciated .
I build an image with dockerfile and I tried to run it with specific network but I received the following error:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"-net=overlay\": executable file not found in $PATH": unknown.
any ideas how to solve this?
Thank you
From your comment, it seems like you docker run command is incorrect, you are passing flag --net=host after the image name which is considered an argument for the container. so --net=host this replaced the "httpd-foreground" command. just try this to understand the scenario
docker run httpd:2.4 echo "hi from the container; will print this message and I will be terminated"
See the last row and this will answer you and you will understand the concept.
docker build -t aaa .
Now run the container and it should work
docker run --net=host aaa
I'm setting up ArchiveBox using the Docker image and instructions found here. Though it appears to have been successfully setup on my computer, I cannot use the main command to add an individual link.
The Setup section instructs you to
clone a github project,
cd into that folder, mkdir data,
chmod 777 it (I'm using Docker for Windows, so I found a Windows equivalent icacls data /grant Everyone:F),
docker-compose up -d,
Finally, To add an individual link run
echo "https://example.com" | docker-compose exec -T archivebox /bin/archive
I expected the outputted archive data to be stored in my data/ volume but it does not appear to be, and I get the following error OCI runtime exec failed: exec failed: container_linux.go:344: starting container process caused "exec format error": unknown
/bin/archive is a path form the docker container and running docker exec with a pathfile actually search the pathfile on your host, and the error ,means your command line can not find archivebox or /bin/archive and run it
I have the below code to build an image
docker build -t provisioner-builder:latest -f images/provisioner/Dockerfile.builder .
Right after this build command I have this line
docker run provisioner-builder:latest /bin/true
The docker run command always throws this error in jenkins
06:23:44 Successfully tagged provisioner-builder:latest
06:23:44 docker run provisioner-builder:latest /bin/true
06:23:45 docker: Error response from daemon: Error response from daemon: pull access denied for provisioner-builder, repository does not exist or may require 'docker login'.
06:23:45 See 'docker run --help'.
SO out of 15 runs in jenkins, the above step fails at-least 10-11 times. I get lucky very rarely. I am not trying to pull image as the image is already present in local [I tested by doing a docker images right after the build command and the image was locally present].
I dont understand why this command fails most of the times.