> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/on-premise/id/on-premise/how-to-guide/maintenance/dockered-maintenance/restarting-dockered-instance.md).

# Memulai ulang instans Docker

Mulai ulang kontainer Navixy Docker menggunakan docker ps untuk menampilkan layanan yang berjalan dan docker restart untuk memuat ulang komponen backend tertentu.

Memulai ulang platform Navixy berbasis Docker mungkin diperlukan dalam berbagai skenario pemecahan masalah dan konfigurasi.

Untuk memulai, Anda harus membuat daftar kontainer di server Anda, termasuk yang sedang berjalan dan yang Berhenti. Hal ini dapat dilakukan menggunakan perintah seperti berikut:

```
docker ps -a
```

Keluaran untuk perintah ini cukup besar dan mendetail, jadi Anda dapat meringkasnya seperti ini:

```
docker ps -a --format "table {{.Names}}\t{{.Status}}"
```

Ini akan menampilkan daftar kontainer dan waktu aktifnya. Untuk memulai ulang salah satunya, Anda perlu menjalankan `docker restart` perintah dan mencantumkan kontainer yang diperlukan. Misalnya, untuk memulai ulang ketiga layanan Java backend, gunakan perintah ini:

```
docker restart navixy-standalone-api-1 navixy-standalone-sms-1 navixy-standalone-tcp-1
```

{% hint style="info" %}
Sebagai alternatif, Anda dapat menggunakan `docker compose restart` perintah dengan mencantumkan kontainer yang diperlukan setelahnya. Dalam hal ini, perintah tersebut melakukan hal yang sama.
{% endhint %}


---

# 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://navixy.com/docs/on-premise/id/on-premise/how-to-guide/maintenance/dockered-maintenance/restarting-dockered-instance.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.