[{"_1":2,"_159":-5,"_160":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_138":139},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_88":-5,"_89":90,"_127":-5,"_128":11,"_129":21,"_130":11,"_131":-5,"_132":11,"_133":-5,"_134":135,"_136":91,"_137":-7},"canonicalUrl","https://hub.docker.com/r/jimmyxian/docker/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","jimmyxian","reponame","docker","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":-5,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":74,"_79":21,"_80":81,"_85":33,"_86":87},"categories",[],"content_types",[44],"image","date_registered","2015-07-27T07:18:46.09242Z","description","","is_private","last_updated","2015-07-27T07:42:59.563153Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.docker.distribution.manifest.v1+prettyjws","name","pull_count",340,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","Docker: the Linux container engine\n==================================\n\nDocker is an open source project to pack, ship and run any application\nas a lightweight container.\n\nDocker containers are both *hardware-agnostic* and *platform-agnostic*.\nThis means they can run anywhere, from your laptop to the largest\nEC2 compute instance and everything in between - and they don't require\nyou to use a particular language, framework or packaging system. That\nmakes them great building blocks for deploying and scaling web apps,\ndatabases, and backend services without depending on a particular stack\nor provider.\n\nDocker began as an open-source implementation of the deployment engine which\npowers [dotCloud](https://dotcloud.com), a popular Platform-as-a-Service.\nIt benefits directly from the experience accumulated over several years\nof large-scale operation and support of hundreds of thousands of\napplications and databases.\n\n![Docker L](docs/static_files/docker-logo-compressed.png \"Docker\")\n\n## Security Disclosure\n\nSecurity is very important to us. If you have any issue regarding security, \nplease disclose the information responsibly by sending an email to \nsecurity@docker.com and not by creating a github issue.\n\n## Better than VMs\n\nA common method for distributing applications and sandboxing their\nexecution is to use virtual machines, or VMs. Typical VM formats are\nVMware's vmdk, Oracle VirtualBox's vdi, and Amazon EC2's ami. In theory\nthese formats should allow every developer to automatically package\ntheir application into a \"machine\" for easy distribution and deployment.\nIn practice, that almost never happens, for a few reasons:\n\n * *Size*: VMs are very large which makes them impractical to store\n and transfer.\n * *Performance*: running VMs consumes significant CPU and memory,\n which makes them impractical in many scenarios, for example local\n development of multi-tier applications, and large-scale deployment\n of cpu and memory-intensive applications on large numbers of\n machines.\n * *Portability*: competing VM environments don't play well with each\n other. Although conversion tools do exist, they are limited and\n add even more overhead.\n * *Hardware-centric*: VMs were designed with machine operators in\n mind, not software developers. As a result, they offer very\n limited tooling for what developers need most: building, testing\n and running their software. For example, VMs offer no facilities\n for application versioning, monitoring, configuration, logging or\n service discovery.\n\nBy contrast, Docker relies on a different sandboxing method known as\n*containerization*. Unlike traditional virtualization, containerization\ntakes place at the kernel level. Most modern operating system kernels\nnow support the primitives necessary for containerization, including\nLinux with [openvz](https://openvz.org),\n[vserver](http://linux-vserver.org) and more recently\n[lxc](https://linuxcontainers.org/), Solaris with\n[zones](https://docs.oracle.com/cd/E26502_01/html/E29024/preface-1.html#scrolltoc),\nand FreeBSD with\n[Jails](https://www.freebsd.org/doc/handbook/jails.html).\n\nDocker builds on top of these low-level primitives to offer developers a\nportable format and runtime environment that solves all four problems.\nDocker containers are small (and their transfer can be optimized with\nlayers), they have basically zero memory and cpu overhead, they are\ncompletely portable, and are designed from the ground up with an\napplication-centric design.\n\nPerhaps best of all, because Docker operates at the OS level, it can still be\nrun inside a VM!\n\n## Plays well with others\n\nDocker does not require you to buy into a particular programming\nlanguage, framework, packaging system, or configuration language.\n\nIs your application a Unix process? Does it use files, tcp connections,\nenvironment variables, standard Unix streams and command-line arguments\nas inputs and outputs? Then Docker can run it.\n\nCan your application's build be expressed as a sequence of such\ncommands? Then Docker can build it.\n\n## Escape dependency hell\n\nA common problem for developers is the difficulty of managing all\ntheir application's dependencies in a simple and automated way.\n\nThis is usually difficult for several reasons:\n\n * *Cross-platform dependencies*. Modern applications often depend on\n a combination of system libraries and binaries, language-specific\n packages, framework-specific modules, internal components\n developed for another project, etc. These dependencies live in\n different \"worlds\" and require different tools - these tools\n typically don't work well with each other, requiring awkward\n custom integrations.\n\n * *Conflicting dependencies*. Different applications may depend on\n different versions of the same dependency. Packaging tools handle\n these situations with various degrees of ease - but they all\n handle them in different and incompatible ways, which again forces\n the developer to do extra work.\n\n * *Custom dependencies*. A developer may need to prepare a custom\n version of their application's dependency. Some packaging systems\n can handle custom versions of a dependency, others can't - and all\n of them handle it differently.\n\n\nDocker solves the problem of dependency hell by giving the developer a simple\nway to express *all* their application's dependencies in one place, while\nstreamlining the process of assembling them. If this makes you think of\n[XKCD 927](https://xkcd.com/927/), don't worry. Docker doesn't\n*replace* your favorite packaging systems. It simply orchestrates\ntheir use in a simple and repeatable way. How does it do that? With\nlayers.\n\nDocker defines a build as running a sequence of Unix commands, one\nafter the other, in the same container. Build commands modify the\ncontents of the container (usually by installing new files on the\nfilesystem), the next command modifies it some more, etc. Since each\nbuild command inherits the result of the previous commands, the\n*order* in which the commands are executed expresses *dependencies*.\n\nHere's a typical Docker build process:\n\n```bash\nFROM ubuntu:12.04\nRUN apt-get update && apt-get install -y python python-pip curl\nRUN curl -sSL https://github.com/shykes/helloflask/archive/master.tar.gz | tar -xzv\nRUN cd helloflask-master && pip install -r requirements.txt\n```\n\nNote that Docker doesn't care *how* dependencies are built - as long\nas they can be built by running a Unix command in a container.\n\n\nGetting started\n===============\n\nDocker can be installed on your local machine as well as servers - both\nbare metal and virtualized. It is available as a binary on most modern\nLinux systems, or as a VM on Windows, Mac and other systems.\n\nWe also offer an [interactive tutorial](https://www.docker.com/tryit/)\nfor quickly learning the basics of using Docker.\n\nFor up-to-date install instructions, see the [Docs](https://docs.docker.com).\n\nUsage examples\n==============\n\nDocker can be used to run short-lived commands, long-running daemons\n(app servers, databases, etc.), interactive shell sessions, etc.\n\nYou can find a [list of real-world\nexamples](https://docs.docker.com/examples/) in the\ndocumentation.\n\nUnder the hood\n--------------\n\nUnder the hood, Docker is built on the following components:\n\n* The\n [cgroups](https://www.kernel.org/doc/Documentation/cgroups/cgroups.txt)\n and\n [namespaces](http://man7.org/linux/man-pages/man7/namespaces.7.html)\n capabilities of the Linux kernel\n* The [Go](https://golang.org) programming language\n* The [Docker Image Specification](https://github.com/docker/docker/blob/master/image/spec/v1.md)\n* The [Libcontainer Specification](https://github.com/docker/libcontainer/blob/master/SPEC.md)\n\nContributing to Docker\n======================\n\n[![GoDoc](https://godoc.org/github.com/docker/docker?status.svg)](https://godoc.org/github.com/docker/docker)\n[![Jenkins Build Status](https://jenkins.dockerproject.org/job/Docker%20Master/badge/icon)](https://jenkins.dockerproject.org/job/Docker%20Master/)\n\nWant to hack on Docker? Awesome! We have [instructions to help you get\nstarted contributing code or documentation](https://docs.docker.com/project/who-written-for/).\n\nThese instructions are probably not perfect, please let us know if anything\nfeels wrong or incomplete. Better yet, submit a PR and improve them yourself.\n\nGetting the development builds\n==============================\n\nWant to run Docker from a master build? You can download \nmaster builds at [master.dockerproject.org](https://master.dockerproject.org). \nThey are updated with each commit merged into the master branch.\n\nDon't know how to use that super cool new feature in the master build? Check\nout the master docs at\n[docs.master.dockerproject.org](http://docs.master.dockerproject.org).\n\nHow the project is run\n======================\n\nDocker is a very, very active project. If you want to learn more about how it is run,\nor want to get more involved, the best place to start is [the project directory](https://github.com/docker/docker/tree/master/project).\n\nWe are always open to suggestions on process improvements, and are always looking for more maintainers.\n\n### Talking to other Docker users and contributors\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n

Internet Relay Chat (IRC)	\n \n IRC a direct line to our most knowledgeable Docker users; we have\n both the `#docker` and `#docker-dev` group on\n irc.freenode.net.\n IRC is a rich chat protocol but it can overwhelm new users. You can search\n our chat archives.\n \n Read our IRC quickstart guide for an easy way to get started.\n
Google Groups	\n There are two groups.\n Docker-user\n is for people using Docker containers.\n The docker-dev\n group is for contributors and other people contributing to the Docker\n project.\n
Twitter	\n You can follow Docker's Twitter feed\n to get updates on our products. You can also tweet us questions or just\n share blogs or stories.\n
Stack Overflow	\n Stack Overflow has over 7000K Docker questions listed. We regularly\n monitor Docker questions\n and so do many other knowledgeable Docker users.\n

\n\n### Legal\n\n*Brought to you courtesy of our legal counsel. For more context,\nplease see the [NOTICE](https://github.com/docker/docker/blob/master/NOTICE) document in this repo.*\n\nUse and transfer of Docker may be subject to certain restrictions by the\nUnited States and other governments.\n\nIt is your responsibility to ensure that your use and/or transfer does not\nviolate applicable laws.\n\nFor more information, please see https://www.bis.doc.gov\n\n\nLicensing\n=========\nDocker is licensed under the Apache License, Version 2.0. See\n[LICENSE](https://github.com/docker/docker/blob/master/LICENSE) for the full\nlicense text.\n\nOther Docker Related Projects\n=============================\nThere are a number of projects under development that are based on Docker's\ncore technology. These projects expand the tooling built around the\nDocker platform to broaden its application and utility.\n\n* [Docker Registry](https://github.com/docker/distribution): Registry \nserver for Docker (hosting/delivery of repositories and images)\n* [Docker Machine](https://github.com/docker/machine): Machine management \nfor a container-centric world\n* [Docker Swarm](https://github.com/docker/swarm): A Docker-native clustering \nsystem\n* [Docker Compose](https://github.com/docker/compose) (formerly Fig): \nDefine and run multi-container apps\n* [Kitematic](https://github.com/kitematic/kitematic): The easiest way to use \nDocker on Mac and Windows\n\nIf you know of another project underway that should be listed here, please help \nus keep this list up-to-date by submitting a PR.\n","has_starred","hub_user","immutable_tags_settings",{"_75":11,"_76":77},"enabled","rules",[78],".*","is_automated","permissions",{"_82":21,"_83":11,"_84":11},"read","write","admin","user","storage_size",502566391,"orgData","recentTags",[91],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_50":110,"_117":94,"_118":33,"_119":56,"_57":120,"_121":122,"_123":108,"_124":110,"_125":66,"_126":21},"content_type","creator",105915,"digest","sha256:b4e79da7beadc190776bd22a4c9d6f1e4a4db125c245d3ef7d6851fb5dc75287","full_size",502425649,"id",637369,"images",[103],{"_104":105,"_95":96,"_106":48,"_107":108,"_109":110,"_111":48,"_112":48,"_113":-5,"_114":115,"_63":66,"_116":-5},"architecture","amd64","features","last_pulled","2026-09-23T08:38:28.892038545Z","last_pushed","2015-07-27T07:43:00Z","os","os_features","os_version","size",517307714,"variant","last_updater","last_updater_username","media_type","latest","repository",267007,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":140,"_147":148,"_134":157,"_158":11},{"_40":141,"_42":142,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":143,"_57":35,"_32":33,"_58":59,"_60":-5,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":144,"_79":21,"_80":146,"_85":33,"_86":87},[],[44],[56],{"_75":11,"_76":145},[78],{"_82":21,"_83":11,"_84":11},"tags",{"_149":64,"_150":-5,"_151":-5,"_152":153},"count","next","previous","results",[154],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_101":155,"_50":110,"_117":94,"_118":33,"_119":56,"_57":120,"_121":122,"_123":108,"_124":110,"_125":66,"_126":21},[156],{"_104":105,"_95":96,"_106":48,"_107":108,"_109":110,"_111":48,"_112":48,"_113":-5,"_114":115,"_63":66,"_116":-5},[],"canDeleteTags","actionData","errors"]

jimmyxian/docker

Tags for jimmyxian/docker