docker-image

问题 I want to implement a Machine Learning algorithm which can operate on homomorphic data using PySEAL library. PySEAL library is released as a docker container with an 'examples.py' file which shows some homomorphic encryption example. I want to edit the 'examples.py' file to implement the ML algorithm. I trying to import a CSV file in this way - dataset = pd.read_csv ('Dataset.csv') I have imported pandas library successfully. I have tried many approaches to import the CSV file but failed. How

问题 On Ubuntu 14.04 (Trusty Tahr) I'm looking for a way to stop a running container and the only information I have is the image name that was used in the Docker run command. Is there a command to find all the matching running containers that match that image name and stop them? 回答1: Following issue 8959, a good start would be: docker ps -a -q --filter="name=<containerName>" Since name refers to the container and not the image name, you would need to use the more recent Docker 1.9 filter ancestor

问题 How do I get the sha256 checksum of an already locally built docker image? I want to use the checksum to annotate a FROM instruction in a derived image: FROM name@sha256:checksum I already tried checksums from docker inspect . Neither the first nor the last of the checksums in the Layers list worked. The one in "Id" did not work. The one in "Parent" did not work. The one in "Container" did not work. The one in "Image" did not work. Some of them I only tried out of desperation to finally find

问题 Dockerfile FROM nginx:1.7 # Deliberately declaring VOLUME before RUN VOLUME /var/tmp RUN touch /var/tmp/test.txt Observation Now I believe I understand the implications of declaring the VOLUME statement before creating test.txt - the volume /var/tmp exposed at runtime will be based on the intermediary container prior to the test.txt file is created so it will be empty (hope this observation is correct) So as expected the following docker run does not show test.txt : docker run kz/test-volume

问题 Is it possible to generate one docker image that will contain many applications? or at least one image that a group many images? My situation is that in our company we have many applications that we know in fact that we will need to deploy them all in the same server, and we need to make very simple the deployment, so deploy image by image is not what we want, so, I am wondering, how can I group them? that only with one command everything should be executed? 回答1: The best practice with Docker

问题 When a Dockerfile contains VOLUME instruction (say) VOLUME [/opt/apache2/www, ...] (hope this path exists in real installation), it means this path is going to be mounted to something (right?). And this VOLUME instruction is for the image and not for one instance of it (container) but for every instance. Anyway irrespective of whether an image contains a VOLUME defined or not, at the time of starting a container the run command can create a volume by mapping a local host path to a container

问题 I have three commands that I am using to "update","re-run", and then "clean up" my current docker image via our CI tool of choice (Jenkins). I'm not including my "container stop and remove" commands for simplicity's sake. docker pull my.private.registry:443/my-awesome-app docker run -d --env-file ./env.list -i -p 8080:8080 -p 9990:9990 my.private.registry:443/my-awesome-app docker rmi $(docker images -f "dangling=true" -q) I'm new to docker-compose and I understand that most of these pull/run

问题 I was wondering if it is possible to offer Docker images, but not allow any access to the internals of the built containers. Basically, the user of the container images can use the services they provide, but can't dig into any of the code within the containers. Call it a way to obfuscate the source code, but also offer a service (the software) to someone on the basis of the container, instead of offering the software itself. Something like "Container as a Service", but with the main advantage

问题 I'm using docker to build images from a docker file. In the process there's some error happened, so the build exit with error code. When I run docker images I can see a untagged image. so I tried to remove it docker rmi xxxxx . But it always fails, it says the images can't be removed because it's used by a stopped container. So I dig a little deeper. I run docker ps -a , now I can see a long list of stopped container which are created when the build process fails. Why there will be container

问题 My understanding is that Docker creates an image layer at every stage of a dockerfile. If I have X containers running on the same machine (where X >=2) and every container has a common underlying image layer (ie. debian), will docker keep only one copy of the base image on that machine, or does it have multiple copies for each container? Is there a point this breaks down, or is it true for every layer in the dockerfile? How does this work? Does Kubernetes affect this in any way? 回答1: Dockers