Slashdot Mirror

← Back to Domains

Domain: docker.io

Stories and comments across the archive that link to docker.io.

Stories · 4

  1. Operating Systems Still Matter In a Containerized World

    Tech · Os · · posted by Soulskill · from the try-to-contain-yourself dept. · 129 comments
    New submitter Jason Baker writes: With the rise of Docker containers as an alternative for deploying complex server-based applications, one might wonder, does the operating system even matter anymore? Certainly the question gets asked periodically. Gordon Haff makes the argument on Opensource.com that the operating system is still very much alive and kicking, and that a hardened, tuned, reliable operating system is just as important to the success of applications as it was in the pre-container data center.

  2. Docker Turns 1: What's the Future For Open Source Container Tech?

    Linux · Software · · posted by timothy · from the within-and-beneath-additional-layers dept. · 65 comments
    darthcamaro (735685) writes "Docker has become one of the most hyped open-source projects in recent years, making it hard to believe the project only started one year ago. In that one year, Docker has now gained the support of Red Hat and other major Linux vendors. What does the future hold for Docker? Will it overtake other forms of virtualization or will it just be a curiosity?"

  3. Ask Slashdot: Scientific Computing Workflow For the Cloud?

    Ask · Cloud · · posted by Soulskill · from the science-as-a-service dept. · 80 comments
    diab0lic writes "I have recently come into the situation where I need to run cloud computing on demand for my research. Amazon's EC2 Spot Instances are an ideal platform for this as I can requisition an appropriate instance for the given experiment {high cpu, high memory, GPU instance} depending on its needs. However I currently spin up the instance manually, set it up, run the experiment, and then terminate manually. This gets tedious monitoring experiments for completion, and I incur unnecessary costs if a job finishes while I'm sleeping, for example. The whole thing really should be automated. I'm looking for a workflow somewhat similar to this:
    1. Manually create Amazon machine image (AMI) for experiment.
    2. Issue command to start AMI on specified spot instance type.
    3. Automatically connect EBS to instance for result storage.
    4. Automatically run specified experiment, bonus if this can be parameterized.
    5. Have AMI automatically terminate itself upon experiment completion.

    Something like docker that spun up on-demand spot instances of a specified type for each run and terminated said instance at run completion would be absolutely perfect. I also know HTCondor can back onto EC2 spot instances but I haven't really been able to find any concise information on how to set up a personal cloud — I also think this is slight overkill. Do any other Slashdot users have similar problems? How did you solve it? What is your workflow? Thanks!"

  4. Docker 0.7 Runs On All Linux Distributions

    Tech · Software · · posted by Soulskill · from the go-big-or-go-home dept. · 88 comments
    rjmarvin writes "Docker 0.7 was released today, with 7 major new features including support to run on all Linux distributions. No longer capable solely on running on Debian and Ubuntu Linux, Docker 0.7 adds support for distributions such as Red Hat, SUSE, Gentoo and Arch. From the announcement: 'A key feature of Docker is the ability to create many copies of the same base filesystem almost instantly. Under the hood Docker makes heavy use of AUFS by Junjiro R. Okajima as a copy-on-write storage mechanism. AUFS is an amazing piece of software and at this point it’s safe to say that it has safely copied billions of containers over the last few years, a great many of them in critical production environments. Unfortunately, AUFS is not part of the standard linux kernel and it’s unclear when it will be merged. This has prevented docker from being available on all Linux systems. Docker 0.7 solves this problem by introducing a storage driver API, and shipping with several drivers. Currently 3 drivers are available: AUFS, VFS (which uses simple directories and copy) and DEVICEMAPPER, developed in collaboration with Alex Larsson and the talented team at Red Hat, which uses an advanced variation of LVM snapshots to implement copy-on-write. An experimental BTRFS driver is also being developed, with even more coming soon: ZFS, Gluster, Ceph, etc. When the docker daemon is started it will automatically select a suitable driver depending on its capabilities.'"