dcp

{
  "aliases": [],
  "alternatives": [],
  "build_dependencies": [
    "rust"
  ],
  "categories": [],
  "caveats": null,
  "conflicts_with": [],
  "dependencies": [],
  "deprecated": 0,
  "deprecation_reason": null,
  "desc": "Docker cp made easy",
  "disable_reason": null,
  "disabled": 0,
  "enrichment_fetched_at": "2026-06-20T23:36:52+00:00",
  "first_seen": "2026-06-20T23:34:18+00:00",
  "full_name": "dcp",
  "github_default_branch": "main",
  "github_last_commit_at": "2023-07-24T01:09:54Z",
  "github_readme_excerpt": "# dcp: docker cp made easy\n\n[![GitHub Actions](https://github.com/exdx/dcp/workflows/ci/badge.svg)](https://github.com/exdx/dcp/actions)\n[![Latest version](https://img.shields.io/crates/v/dcp.svg)](https://crates.io/crates/dcp)\n[![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE)\n\n## Summary\n\nContainers are great tools that can encapsulate an application and its dependencies,\nallowing apps to run anywhere in a streamlined way. Some container images contain\ncommands to start a long-lived binary, whereas others may simply contain data\nthat needs to be available in the environment (for example, a Kubernetes cluster).\nFor example, [operator-framework bundles](https://olm.operatorframework.io/docs/tasks/creating-operator-bundle/) and [crossplane packages](https://crossplane.io/docs/v1.9/concepts/packages.html) both use\ncontainer images to store Kubernetes manifests. These manifests are unpacked and applied to the cluster.\n\nOne of the downsides of using container images to store data is that they are\nopaque. There\u0027s no way to quickly tell what\u0027s inside the image, although\nthe hash digest is useful in seeing whether the image has changed from a previous\nversion. The options are to use `docker cp` or something similar using podman\nor containerd.\n\nUsing `docker cp` by itself can be cumbersome. Say you have a remote image\nsomewhere in a registry. You have to pull the image, create a container from that\nimage, and only then run `docker cp \u003ccontainer-id\u003e` using an unintuitive syntax for selecting\nwhat should be copied to the local filesystem.\n\ndcp is a simple binary that simplifies this workflow. A user can simply\nsay `dcp \u003cimage-name\u003e` and dcp can extract the contents of that image onto the\nlocal filesystem. From there, users are free to view and edit the files locally. Any OCI-based image is supported. \n\n![Demo](demo.gif)\n\n## Installing\n\n### Installing from crates.io\n\nIf you\u0027re a Rust programmer and have Rust installed locally, you can install dcp\nb",
  "github_repo": "exdx/dcp",
  "github_stars": 114,
  "github_topics": [
    "containers",
    "docker",
    "docker-image",
    "kubernetes"
  ],
  "homepage": "https://github.com/exdx/dcp",
  "homepage_og_description": null,
  "homepage_og_image": null,
  "homepage_title": null,
  "installs_30d": 6,
  "installs_365d": 129,
  "installs_90d": 21,
  "keg_only": 0,
  "keg_only_reason": null,
  "last_seen": "2026-06-20T23:34:18+00:00",
  "license": "MIT",
  "llm_generated_at": null,
  "llm_model": null,
  "name": "dcp",
  "oldnames": [],
  "one_liner": null,
  "optional_dependencies": [],
  "rank_30d": 10160,
  "rank_365d": 8503,
  "rank_90d": 9570,
  "raw_hash": "83ab8cd654ac14aa",
  "recommended_dependencies": [],
  "revision": 0,
  "ruby_source_path": "Formula/d/dcp.rb",
  "tap": "homebrew/core",
  "test_dependencies": [],
  "uses_from_macos": [],
  "version_head": "HEAD",
  "version_stable": "0.4.1",
  "versioned_formulae": [],
  "why_use_this": null
}