containers

I'm confused about docker swarm. As far as I know, the old way to run a swarm was to run manager and workers in containers, before docker engine provided native support for swarm mode. Documentation for the old, containerized swarm explained how to setup service discovery using consul, etcd or zookeeper. Service discovery is necessary, as services are ran at random ports to avoid collisions, right? Documentation for the docker engine swarm mode doesn't explain how to setup service discovery. Now I'm confused, if the mechanism is included in swarm mode, or is the documentation incomplete. Where

I've managed to wrap my head around some of C++'s functional capacities (for_each, mapping functions, using iterators...) but the construction of the templates and function argument lists for taking in generic containers and iterators still eludes me. I have a practical example I'm hoping someone can illustrate for me: Take the following function that processes an incoming std::vector and builds a running total of many data-points/iterations of a process: /* the for-loop method - not very savvy */ void UpdateRunningTotal (int_vec& total, int_vec& data_point) { for (int i = 0; i < V_SIZE; i++)

During my Docker container build process, I attemptted to install a few packages using apt-get install. However the process failed to complete because the 3 of the 4 packages could not be found. Step 1 : RUN apt-get update && apt-get install -y netcat ca-certificates build-essential libssl-dev ---> Running in 38d22d97ec4a Err http://http.debian.net jessie InRelease Err http://http.debian.net jessie-updates InRelease Err http://security.debian.org jessie/updates InRelease Err http://http.debian.net jessie Release.gpg Could not resolve 'http.debian.net' Err http://security.debian.org jessie

Is there a standard container that has the same general API as vector<T> but that populates new locations via direct default construction? Background: I have a type that disallows copying but has a default constructor and what I really want to do is this: vector<NoCopy> bag(some_size); // use bag[i]'s return; // bag & contents get correctly cleaned up. However, this doesn't work because vector<T>(int) is implemented in terms of default constructing an object and then copying it into each of the new locations. Edit: Not C++0xB (a.k.a. C++11) One option would be to upgrade to a C++11-compliant

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 that the developer can use these container(s) for local development too, but with no access to the

I have installed mongodb on a docker container together with openssh on ubuntu 14.04. The container is running with ssh but when I ssh into the container I get the following error when trying to start mongod. root@430f9502ba2d:~# service mongod start Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service mongod start Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the start(8) utility, e.g. start mongod Also start mongod does not affect anything. Tried looking at this also Mongo daemon doesn't run by

Is it possible, to pull private images from Docker Hub to a Google Cloud Kubernetes cluster? Is this recommended, or do I need to push my private images also to Google Cloud? I read the documentation, but I found nothing that could explain me this clearly. It seems that it is possible, but I don´t know if it's recommended. There is no restriction to use any registry you want. If you just use the image name, (e.g., image: nginx) in pod specification, the image will be pulled from public docker hub registry with tag assumed as :latest As mentioned in the Kubernetes documentation : The image