github.com/containers/podman/v5@v5.1.0-rc1/docs/source/locale/ja/LC_MESSAGES/Introduction.po (about)

     1  # This file is distributed under the same license as the Podman package.
     2  # Translators:
     3  # Takuya Nishimura <tanishim@redhat.com>, 2023.
     4  msgid ""
     5  msgstr ""
     6  "Project-Id-Version: Podman \n"
     7  "Report-Msgid-Bugs-To: \n"
     8  "POT-Creation-Date: 2023-08-29 22:22+0900\n"
     9  "PO-Revision-Date: 2023-08-29 22:22+0900\n"
    10  "Last-Translator: Takuya Nishimura <tanishim@redhat.com>\n"
    11  "Language: ja\n"
    12  "Language-Team: ja\n"
    13  "Plural-Forms: nplurals=1; plural=0;\n"
    14  "MIME-Version: 1.0\n"
    15  "Content-Type: text/plain; charset=utf-8\n"
    16  "Content-Transfer-Encoding: 8bit\n"
    17  "Generated-By: Babel 2.12.1\n"
    18  
    19  #: ../../source/Introduction.rst:4
    20  msgid "Introduction"
    21  msgstr "はじめに"
    22  
    23  #: ../../source/Introduction.rst:5
    24  msgid ""
    25  "Containers_ simplify the production, distribution, discoverability, and "
    26  "usage of applications with all of their dependencies and default "
    27  "configuration files. Users test drive or deploy a new application with "
    28  "one or two commands instead of following pages of installation "
    29  "instructions. Here's how to find your first `Container Image`_::"
    30  msgstr ""
    31  
    32  #: ../../source/Introduction.rst:9 ../../source/Introduction.rst:23
    33  #: ../../source/Introduction.rst:46 ../../source/Introduction.rst:73
    34  #: ../../source/Introduction.rst:89
    35  msgid "Output::"
    36  msgstr ""
    37  
    38  #: ../../source/Introduction.rst:17
    39  msgid ""
    40  "The previous command returned a list of publicly available container "
    41  "images on DockerHub. These container images are easy to consume, but of "
    42  "differing levels of quality and maintenance. Let’s use the first one "
    43  "listed because it seems to be well maintained."
    44  msgstr ""
    45  
    46  #: ../../source/Introduction.rst:19
    47  msgid "To run the busybox container image, it’s just a single command::"
    48  msgstr ""
    49  
    50  #: ../../source/Introduction.rst:27
    51  msgid ""
    52  "You can poke around in the busybox container for a while, but you’ll "
    53  "quickly find that running small container with a few Linux utilities in "
    54  "it provides limited value, so exit out::"
    55  msgstr ""
    56  
    57  #: ../../source/Introduction.rst:31
    58  msgid ""
    59  "There’s an old saying that “nobody runs an operating system just to run "
    60  "an operating system” and the same is true with containers. It’s the "
    61  "workload running on top of an operating system or in a container that’s "
    62  "interesting and valuable."
    63  msgstr ""
    64  
    65  #: ../../source/Introduction.rst:33
    66  msgid ""
    67  "Sometimes we can find a publicly available container image for the exact "
    68  "workload we’re looking for and it will already be packaged exactly how we"
    69  " want. But, more often than not, there’s something that we want to add, "
    70  "remove, or customize. It can be as simple as a configuration setting for "
    71  "security or performance, or as complex as adding a complex workload. "
    72  "Either way, containers make it fairly easy to make the changes we need."
    73  msgstr ""
    74  
    75  #: ../../source/Introduction.rst:35
    76  msgid ""
    77  "Container Images aren’t actually images, they’re repositories often made "
    78  "up of multiple layers. These layers can easily be added, saved, and "
    79  "shared with others by using a Containerfile (Dockerfile). This single "
    80  "file often contains all the instructions needed to build a new container "
    81  "image and can easily be shared with others publicly using tools like "
    82  "GitHub."
    83  msgstr ""
    84  
    85  #: ../../source/Introduction.rst:37
    86  msgid ""
    87  "Here's an example of how to build a Nginx web server on top of a Debian "
    88  "base image using the Dockerfile maintained by Nginx and published in "
    89  "GitHub::"
    90  msgstr ""
    91  
    92  #: ../../source/Introduction.rst:41
    93  msgid ""
    94  "Once, the image build completes, it’s easy to run the new image from our "
    95  "local cache::"
    96  msgstr ""
    97  
    98  #: ../../source/Introduction.rst:52
    99  msgid ""
   100  "Building new images is great, but sharing our work with others lets them "
   101  "review our work, critique how we built them, and offer improved versions."
   102  " Our newly built Nginx image can be published at quay.io or docker.io to "
   103  "share it with the world. Everything needed to run the Nginx application "
   104  "is provided in the container image. Others can easily pull it down and "
   105  "use it, or make improvements to it."
   106  msgstr ""
   107  
   108  #: ../../source/Introduction.rst:54
   109  msgid ""
   110  "Standardizing on container images and `Container Registries`_ enable a "
   111  "new level of collaboration through simple consumption. This simple "
   112  "consumption model is possible because every major Container Engine and "
   113  "Registry Server uses the Open Containers Initiative (OCI_) format. This "
   114  "allows users to find, run, build, share and deploy containers anywhere "
   115  "they want. Podman and other `Container Engines`_ like CRI-O, Docker, or "
   116  "containerd can create and consume container images from docker.io, "
   117  "quay.io, an on premise registry or even one provided by a cloud provider."
   118  " The OCI image format facilitates this ecosystem through a single "
   119  "standard."
   120  msgstr ""
   121  
   122  #: ../../source/Introduction.rst:56
   123  msgid ""
   124  "For example, if we wanted to share our newly built Nginx container image "
   125  "on quay.io it’s easy. First log in to quay::"
   126  msgstr ""
   127  
   128  #: ../../source/Introduction.rst:59
   129  msgid "Input::"
   130  msgstr ""
   131  
   132  #: ../../source/Introduction.rst:65
   133  msgid "Next, tag the image so that we can push it into our user account::"
   134  msgstr ""
   135  
   136  #: ../../source/Introduction.rst:69
   137  msgid "Finally, push the image::"
   138  msgstr ""
   139  
   140  #: ../../source/Introduction.rst:85
   141  msgid ""
   142  "Notice that we pushed four layers to our registry and now it’s available "
   143  "for others to share. Take a quick look::"
   144  msgstr ""
   145  
   146  #: ../../source/Introduction.rst:99
   147  msgid ""
   148  "To summarize, Podman makes it easy to find, run, build and share "
   149  "containers."
   150  msgstr ""
   151  
   152  #: ../../source/Introduction.rst:101
   153  msgid ""
   154  "Find: whether finding a container on dockerhub.io or quay.io, an internal"
   155  " registry server, or directly from a vendor, a couple of `podman "
   156  "search`_, and `podman pull`_ commands make it easy"
   157  msgstr ""
   158  
   159  #: ../../source/Introduction.rst:102
   160  msgid ""
   161  "Run: it's easy to consume pre-built images with everything needed to run "
   162  "an entire application, or start from a Linux distribution base image with"
   163  " the `podman run`_ command"
   164  msgstr ""
   165  
   166  #: ../../source/Introduction.rst:103
   167  msgid ""
   168  "Build: creating new layers with small tweaks, or major overhauls is easy "
   169  "with `podman build`_"
   170  msgstr ""
   171  
   172  #: ../../source/Introduction.rst:104
   173  msgid ""
   174  "Share: Podman lets you push your newly built containers anywhere you want"
   175  " with a single `podman push`_ command"
   176  msgstr ""
   177  
   178  #: ../../source/Introduction.rst:106
   179  msgid ""
   180  "For more instructions on use cases, take a look at our :doc:`Tutorials` "
   181  "page."
   182  msgstr ""