> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/core/get-started/faq/dotnetcore-to-work-on-docker.md).

# How can I get the .NET SDK to work on Docker?

Instructions to get Apryse .NET SDK to work with Docker.

The project needs to know where the shared lib is located. You can achieve this by any one of the following 2 approaches.

Approach 1:

You will add the following to the Docker file: ​ `COPY libPDFNet* /usr/lib/ RUN rm /usr/lib/libPDFNetC.so;\ mv /usr/lib/libPDFNetC.so.6.10.0 /usr/lib/libPDFNetC.so`

Adding the above commands will resolve the following two issues:

1. Apryse's native library needs to be placed directly in `"/usr/lib/"` folder
2. Docker does not like how we symlink the so files, so removing the `symlink` is required

Approach 2:

1. Manually remove the symlink `libPDFNetC.so` and rename the versioned so to `libPDFNetC.so`
2. Edit the `.csproj` file to directly point to `libPDFNetC.so`

{% tabs %}
{% tab title="XML" %}
{% code lineNumbers="true" %}

```xml
<Content Include="/src/MyApp/libPDFNetC.so">
    <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
</Content>
```

{% endcode %}
{% endtab %}
{% endtabs %}


---

# 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.apryse.com/core/get-started/faq/dotnetcore-to-work-on-docker.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.