Local files COPY-ed into the image will have “ -rwxr-xr-x” permissions in the container.But on Windows the local files that might get COPY-ed into the image may have Windows line endings (crlf), and that can cause breakage within the container. The Docker container is Linux and expects Unix line endings (lf).There’s some awkwardness when working with Docker on Windows. Running docker build a lot will often cause the same packages to be repeatedly downloaded from remote package sources. The network and remote packages sources are getting a workout.Ĭreating well-formed containers typically requires attempting many variations of the Docker file. While going through these examples and trying other experiments, I noticed a couple things: And the second example from the Lees-Miller gentle introduction to containers and Docker is also there, in recipes/Docker Demo - latex runner. But the example from the last post is there, in recipes/Docker Demo - simple web app. It quickly became evident that was too ambitious and I needed to start smaller, and so I did, trying many simple scenarios. That branch name reflects my initial idea to put the LLVM tool chain on a container and use that container for experimenting with LLVM and clang. Currently the t-dev/llvmrecipe branch is where active development is going on. It’s in a GitHub repository JeNeSuisPasDave/docker-recipes. I’m keeping a record of what I do as I’m learning to use containers. When I use the OS X Activity Monitor (something like Windows Task Manager) I see the real metrics, which does show the guest VM consuming all that CPU, not my Terminal session. The CPU utilization menu widget will list the top 5 processes consuming CPU and it was report Terminal at 100%. I use an application called iStat Menus to provide system and device status information in the OS X menu bar. After finding the time for a closer investigation, I find that it is not Terminal that was using all that CPU but rather the VBoxHeadless process (i.e., the guest VM process). In the last post I noted that I saw the Terminal process on my Mac jump up to 100% CPU during a docker build while the sinatra gem was being installed. I explain what I’m working on that is related to automating software development, or related to software development in general.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |