> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/admin/configuring-a-self-hosted-instance/enable-output-to-container-artifacts.md).

# Enabling the option to write output data to a container repository

For PostgreSQL, MySQL, and SQL Server workspaces, you can configure Tonic Structural to write destination data to a container repository instead of to a database server. For more information, go to [Writing output to a container repository](/app/workspace/workspace-configuration-settings/workspace-config-write-to-container-artifacts.md).

If Structural is deployed on Kubernetes, then the option is supported automatically.

If Structural is deployed on Docker, then to enable the option, you can set up a separate Kubernetes cluster to use specifically for that purpose.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Set up a Kubernetes cluster</strong></td><td>On a Docker instance, set up a separate Kubernetes cluster to use.</td><td></td><td><a href="/app/admin/configuring-a-self-hosted-instance/enable-output-to-container-artifacts/container-output-separate-kubernetes-cluster.md">Setting up a Kubernetes cluster to use to write output data to a container repository</a></td></tr><tr><td><strong>Grant required permissions</strong></td><td>Ensure that Structural has the required permissions to write destination data to container repositories.</td><td></td><td><a href="/app/admin/configuring-a-self-hosted-instance/enable-output-to-container-artifacts/kubernetes-required-containerization-access.md">Required access to write destination data to a container repository</a></td></tr></tbody></table>


---

# 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.tonic.ai/app/admin/configuring-a-self-hosted-instance/enable-output-to-container-artifacts.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.