> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/keeper-connection-manager/jp/installation/auto-docker-install/adding-packages.md).

# パッケージの追加

Docker自動インストールメソッドで追加パッケージを有効化

Docker自動インストール方式を使用する場合、生成されたDocker Composeファイルを直接変更することでパッケージを追加できます。SSOまたはLDAP対応の追加はこの手順で行います。

Keeperコネクションマネージャーの環境を変更するには、以下の場所にある `docker-compose.yml` ファイルを編集します。

**`/etc/kcm-setup/docker-compose.yml`**

**設定の変更を適用する**

`kcm-setup.run` スクリプトには `apply` 機能があり、コンテナを更新せずに設定の変更を適用できます。Linuxコマンド ラインから、curlコマンドを使用して最新のインストーラースクリプトに更新します。

```
curl -O https://keepersecurity.com/kcm/kcm-setup.run
```

変更を適用します。

```
sudo ./kcm-setup.run apply
```

**コンテナを更新して再起動します**

環境を更新するには、`kcm-setup.run upgrade` コマンドを使用してコンテナを更新し、最新の設定を使用して起動します。

```
sudo ./kcm-setup.run stop
sudo ./kcm-setup.run upgrade
```

または以下を行います。

```
sudo su
cd /etc/kcm-setup/
docker-compose -p kcm up -d
```

<figure><img src="https://4041518992-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ7s6LQJaKa1G17O787JG%2Fuploads%2FZS3SdjdHZOJdqopqIVjF%2Fimage.png?alt=media&amp;token=00ffc94c-ec42-47ce-ae21-667d8c965c71" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/keeper-connection-manager/jp/installation/auto-docker-install/adding-packages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
