Dependency injection container for javascript
InversifyJs container
Check if the process is running inside a container (Docker/Podman)
Opentelemetry resource detector to get container resource attributes
Container Helper for Victory
vaadin-input-container
Google Container Engine API client for Node.js
A plugin for Tailwind CSS v3.2+ that provides utilities for container queries.
Check if the process is running inside a Docker container
Tab container element
Container utilities in the Garden Design System
Declare a list of container queries in a single at-container rule
Fluid container definitions
container plugin for MarkdownIt
Predictable state container for JavaScript apps
A CLI Multi-Tab Container Utilizing Labels For Blessed
Cloudflare Style Container
Parse container info from cgroups file
Lightweight dependency injection container for JavaScript/TypeScript
Container Query for React Component
@usewaypoint/document compatible Container component
VuePress plugin for markdown container
container
Fluid container loader
a container lib
A complete library to interact with Tag Manager (protocol v2)
Python bindings to the docker-api-rs crate
Docker/Container component for rust-camel — run, manage and listen to container events via the Camel routing engine
Elegant and extensible assertions in rust.
Abstract over "containers" that hold a T, such as a T itself, Box<T>, or Arc<Mutex<T>>
A modern, feature-rich testing framework for Rust with Docker integration
An intuitive Docker management CLI built in Rust with full Docker command parity
A complete library to interact with Tag Manager (protocol v2)
The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.42) is used. For example, calling `/info` is the same as calling `/v1.42/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```
Fluent test assertions
A complete library to interact with Tag Manager (protocol v1)
A simple, configurable object container implemented in Ruby
Abstract container-based parallelism using threads and processes where appropriate.
Handy Ruby object container for cleaner views
The Ruby Container for Henry
This is the simple REST client for Kubernetes Engine API V1. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the Kubernetes Engine API, but note that some services may provide a separate modern client that is easier to use.
This is the simple REST client for Kubernetes Engine API V1beta1. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the Kubernetes Engine API, but note that some services may provide a separate modern client that is easier to use.
container_ship is a simple ECS deployment tool. You only need to prepare Dockerfile and task_definition.json
Builds and manages container-based applications, powered by the open source Kubernetes technology.
Thread-safe semanticaly-defined IoC/DI Container
Fetch, Upload, Organize, and Distribute Software Packages
Loads container configuration values from environment variables, secrets, and credentials.
A supervisor for managing multiple container processes.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.