Since docker-modem is not really useable currently especially with the new cluster volumes, this project aims to integrate all of the features that docker-modem does not.
import { Modem } from "docker-api-nodejs";
const modem = new Modem(<path-to-docker-socket>);
The project uses the responses from docker in a handle model. That means that for a basic request such as listing object like volumes you will get the exact same response as you would when you call the socket directly.
Hoever if you want to get specific information on an object e.g. inspecting its content more closely you can create a handle for that object like so:
Handle for a volume:
const volumeHandle = new VolumeHandle(<modem>, <name of the volume>);
const clusterVolumeHandle = new ClusterVolumeHandle(<modem>, <id of the clusterVolume>);
Create functions always return a handle:
const handle = await Configs.create(<modem>, <configSpec>);
Alternatively you can always get a handle on an object by calling its from<Object> function:
const handle = NodeHandle.fromNode(<modem>, <node-object>);
From there on you can (if the object supports it) inspect, remove, update, ...
The parameters for every operation are based on the official docker api documentation
Stacks are handled a little different as there is no endpoint in the docker socket to connect to. See here for more details
Testing assumes a clean docker environment with no objects other than the standard. So if you want to test the project keep that in mind
Licensed under the Apache license, version 2.0 (the "license"); You may not use this file except in compliance with the license. You may obtain a copy of the license at:
http://www.apache.org/licenses/LICENSE-2.0.html
Unless required by applicable law or agreed to in writing, software distributed under the license is distributed on an "as is" basis, without warranties or conditions of any kind, either express or implied. See the license for the specific language governing permissions and limitations under the license.