https://github.com/taskcluster/docker-services

Run a command for a docker image with all of its linked dependencies
https://github.com/taskcluster/docker-services

Last synced: 5 days ago
JSON representation

Run a command for a docker image with all of its linked dependencies

• Host: GitHub
• URL: https://github.com/taskcluster/docker-services
• Owner: taskcluster
• Archived: true
• Created: 2014-01-22T04:47:09.000Z (almost 11 years ago)
• Default Branch: master
• Last Pushed: 2014-01-28T10:09:33.000Z (almost 11 years ago)
• Last Synced: 2024-10-01T11:39:33.273Z (about 1 month ago)
• Language: JavaScript
• Size: 4.7 MB
• Stars: 4
• Watchers: 9
• Forks: 2
• Open Issues: 2
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• awesome-starred - taskcluster/docker-services - Run a command for a docker image with all of its linked dependencies (others)

README

        
# docker-services

Docker orchestration library (written in node) for testing

docker images. Images can depend on other images, etc...

## Examples

See [/examples](/examples) for the full list of fully functional (and

tested) examples.

Lets say you have a node application which has a worker and uses both

use amqp.

`docker_services.json`:

```json

{

  "app": {

    "links": ["worker:worker", "amqp:amqp"],

    "image": "my-repo/my-app"

  },

  "worker": {

    "links": ["amqp:amqp"],

    "image": "my-repo/worker"

  },

  "amqp": {

    "image": "some-lib/amqp"

  }

}

```

Then you could run a test on in the app like this:

```sh

docker-services exec app npm test

```

## Commands

### exec

`docker-services exec  [options]` handles bring up and down of dependencies but has the capabilities as the `docker run` command (creates a docker subshell with the correct options).

## Known issues

  - docker must be on the host (meaning you must be on linux). This will be fixed soon.

  - because of how `exec` is implemented (without knowledge of docker options) you must pass parameteres in (IMO)

    correctly do this: `exec -e=VALUE=yey` not this `-e VALUE=yey` bad things will happen.

## Roadmap

  - Remove the need for docker to run on the host

  - Aggregate log output for exec (so we can see other services while running exec)

  - Formal support for `up` and `down` for deamonized services (you won't need to leave exec running)

  - Building of docker images

## Developing

You need [vagrant](http://www.vagrantup.com/).

## Running the tests

```sh

vagrant up

vagrant ssh

cd /vagrant

make test

```

## Publishing a new version

The 'associate' is a docker image that also needs to be published

for each version (right now this is tied to my docker account).