docker-cmd-js

Apparently running a docker in the cmd.exe requires a bunch of environment variables set up. Just spawning a spawnSync from child_process won't do in most cases. Thus the birth of this lib.

Besides, command execution is wrapped in Promises, and there are some helper methods one can use. See API.

Why?

What if you have multiple commands that you always run to set up your environment or to deploy a project to AWS? This is where this project comes in handy.

Show me code!

Example to deply an app to AWS

var gulp = require('gulp');
var dockerCmdJs = require('docker-cmd-js');
var cmd = new dockerCmdJs.Cmd();
 
gulp.task('deploy', (done) => {
    cmd.debug().run('aws ecr get-login --region us-east-1', true)
        .then((authCmd)=> cmd.run(authCmd))
        .then(()=> cmd.run('docker build -t myapp .'))
        .then(()=> cmd.run('docker tag myapp:latest someawsid.dkr.ecr.us-east-1.amazonaws.com/myapp:latest'))
        .then(()=> cmd.run('docker push someawsid.dkr.ecr.us-east-1.amazonaws.com/myapp:latest'))
        .catch((err) => { console.log(err); })
        .finally(() => { done() });
});

API

new dockerCmdJs.Cmd(machineName?: string)

Instantiates object that'll run commands. Optionally you can set machine name against which commands will run.

---

cmd.debug(): dockerCmdJs.Cmd

Sets verbose output.

---

cmd.run(command: string, noNewLines?: boolean): Promise<string>

Takes any command as string. Parameter noNewLines set to true removes cariage returns from the output.

Returns Promise.

---

cmd.runSync(command: string): RunResult;

Takes any command as string.

Returns the following object:

interface RunResult {
    stdOut: string;
    stdErr: string;
}
 

---

cmd.resToJSON(s: string): any[]

Whenever a command run that returns a tabular data (ex: docker images), you can pass the result to this method, which will convert data into JSON. Example:

cmd.run('docker images').then(
    (res)=> {
        let json = cmd.resToJSON(res);
    },
    (err)=> { console.log(err); }
);

---

cmd.machine

cmd.machine.start.hyperv(opts: IStartOpts): Promise<{}>

Starts machine. If it does not exist, it'll be created with hyperv driver. Resolves even if machine is already started.

cmd.machine.start.virtualbox(opts: IStartOpts): Promise<{}>

Starts machine. If it does not exist, it'll be created with virtualbox driver. Resolves even if machine is already started.

---

cmd.machine.ipAddress(): Promise<string>

Returns machine's IP address.

---

cmd.machine.status(): Promise<string>

Returns machine's status.

---

cmd.machine.remove(): Promise<string>

Removes machine.

---

cmd.image

cmd.image.build(imageName: string, opts?: IBuildImageOpts): Promise<{}>

Builds desired image. Unless instructions on how to build are not provided via options, and an image with such name is found, it'll prompt you asking what you want to do. You can provide object with the following options:

export interface IBuildImageOpts {
    /*
     * set path or url to Dockerfile. If not specified assumes current directory.
    */
    pathOrUrl?: string;
    /*
     * regular build using cache.
    */
    regularBuild?: boolean; 
    /*
     * delete cache and previous image. Build from scratch.
    */
    freshBuild?: boolean;
    /*
     * skips build the image if it already exists
    */
    buildOnlyIfMissing?: boolean;
}

---

cmd.image.remove(imageName: any): Promise<string>

Removes desired image

---

cmd.image.checkForDangling(): Promise<{}>

Checks for dangling images. If found, prompts with question whether to remove them or not.

---

cmd.container

cmd.container.start(imageName: any, opts?: IStartDockerOpts, command?: string, extraOpts?: IStartExtraOpts): Promise<boolean>

Starts container from desired image. Returns a Promise of boolean stating whether the container was already started. You can provide object with the following options. See docker docs for options' description:

export interface IStartDockerOpts {
    name?: string;
    publish?: string[];
    volume?: string;
    volumesFrom?: string[];
    link?: string[];
    env?: string[];
}

You can also provide additional options:

export interface IStartExtraOpts {
  startFresh?: boolean;
}

Setting startFresh to true will remove container if it exists, build, and start it.

---

cmd.container.remove(containerName: string): Promise<boolean>

Removes container with option --force.

---

cmd.container.status(containerName: string): Promise<string>

Returns container's status.

---

cmd.container.waitForPort(opts: IWaitForPortOpts): Promise;

Resolves when desired port becomes awailable.

Useful for when container's services take time to start up after the container started. Ex: starting up container FROM mysql

interface IWaitForPortOpts {
    port: number;
    host?: string;
    retryIntervalMs?: number;
    timeoutMs?: number;
}

---

cmd.volume

cmd.volume.create(opts?: ICreateVolumeOpts, advOpts?: ICreateVolumeAdvOpts): Promise<string>

Creates a volume

Parameter opts - represents docker options for this command Parameter advOpts:

interface ICreateVolumeAdvOpts {
    // create volume only if it's missing. Otherwise resolve its name.
    createOnlyIfMissing?: boolean;
}

---

cmd.volume.inspect(volumeName: any): Promise<IInspectVolumeItemResult[]>

Returns volumes's details.

interface IInspectVolumeItemResult {
    Name: string;
    Driver: string;
    Mountpoint: string;
}

---

cmd.volume.remove(volumeName: string): Promise<string>

Removes a volume with desired name.

---

Credits

Thanks to Matt Klein, who started out coding this lib.