> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/9.3-install/pentaho-installation-overview-cp/docker-container-deployment-of-pentaho-installation-cp/using-dockmaker-with-service-packs.md).

# Using DockMaker with service packs

The DockMaker command line tool does not support the service pack (SP) update installers. You must use the full SP artifacts. To use these artifacts, first download them directly from the `DockMaker Full Artifacts` directory within each service pack release article. Then, copy them to the `artifactCache` directory or to another directory as defined by the **docker.server.artifactCache** property in the `Dockmaker.properties` file. The following shows example artifact file downloads that are available for the 9.3 release:

Server:

* `pentaho-server-ee-9.3.0.4-733-dist.zip`
* `paz-plugin-ee-9.3.0.4-733-dist` if **paz** is in the command line
* `pdd-plugin-ee-9.3.0.4-733-dist` if **pdd** is in the command line
* `pir-plugin-ee-9.3.0.4-733-dist` if **pir** is in the command line
* Any `.kar` files that you have specified in the command line, for example, `pentaho-hadoop-shims-ee-cdpdc71-kar-9.3.0.4-733-dist`

PDI client, Carte:

* `pdi-ee-client-9.3.0.4-733-dist`
* Hadoop add-ons for Pentaho 9.5 or greater
* Any `.kar` files specified in the command line, for example, `pentaho-hadoop-shims-ee-cdpdc71-kar-9.3.0.4-733-dist`


---

# 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.pentaho.com/install/9.3-install/pentaho-installation-overview-cp/docker-container-deployment-of-pentaho-installation-cp/using-dockmaker-with-service-packs.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.
