https://github.com/lightsofapollo/dockerhost-client
Docker Host Worker Client
https://github.com/lightsofapollo/dockerhost-client
Last synced: 8 months ago
JSON representation
Docker Host Worker Client
- Host: GitHub
- URL: https://github.com/lightsofapollo/dockerhost-client
- Owner: lightsofapollo
- Created: 2014-11-02T05:35:02.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2015-05-06T04:18:05.000Z (about 11 years ago)
- Last Synced: 2024-12-27T15:12:52.044Z (over 1 year ago)
- Language: JavaScript
- Size: 152 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
dockerhost-client
=================
This is a prototype things are buggy and may require manual fiddling...
My goal here is to have some people try this and vet the idea of using a
model close to this for loaner machines... If this works then we can
make it nice !
## Requirements
- node 0.10 or greater
- TASKCLUSTER_CLIENT_ID must be set and valid (go to http://auths.taskcluster.net/ to get tokens)
- TASKCLUSTER_ACCESS_TOKEN must be set and valid (go to http://auths.taskcluster.net/ to get tokens)
- docker client (try `which docker`) >= 1.3
## Try me
Create global aliases
```sh
npm link
```
```sh
# tc-docker allows _multiple_ docker hosts specificied by alias (in this
# case the alias is remote) if this alias has not been created yet it
# provisions it on AWS then runs whatever commands you specify.
tc-docker remote ps
```
Things to test:
- build times (try `tc-docker remote build ...`)
- using docker-exec (requires docker client 1.3!)
- -v (remember -v is not mounting from your local machine!)
## Other commands
See `tc-docker-admin` this contains the logic to create/manage the
directories which have the docker ssh keys, etc... The admin is very
incomplete but will allow you to "unstuck" yourself if tc-docker
breaks..
## But what if some other program is using the `docker` executable?
So you want to use your remote docker instance but the `docker` command
is expected to be used? Easy:
```sh
# Make sure your remote exists
tc-docker remote version
source ~/.tc-docker/remote/activate
```
Now when you invoke `docker` it shall use the remote docker instance.