> For the complete documentation index, see [llms.txt](https://data-programs.gitbook.io/singularity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://data-programs.gitbook.io/singularity/kr/cli-reference/storage/create/opendrive.md).

# Opendrive

{% code fullWidth="true" %}

```
이름:
   singularity storage create opendrive - OpenDrive

사용법:
   singularity storage create opendrive [command options] [arguments...]

설명:
   --username
      사용자 이름.

   --password
      비밀번호.

   --encoding
      백엔드의 인코딩입니다.
      
      자세한 내용은 [개요의 인코딩 섹션](/overview/#encoding)을 참조하십시오.

   --chunk-size
      파일은 이 크기로 청크 단위로 업로드됩니다.
      
      이 청크는 메모리에 버퍼링되므로 늘리면
      메모리 사용량이 증가합니다.


옵션:
   --help, -h        도움말 표시
   --password value  비밀번호. [$PASSWORD]
   --username value  사용자 이름. [$USERNAME]

   고급

   --chunk-size value  파일을 이 크기로 청크 단위로 업로드합니다. (기본값: "10Mi") [$CHUNK_SIZE]
   --encoding value    백엔드의 인코딩입니다. (기본값: "Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,LeftSpace,LeftCrLfHtVt,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot") [$ENCODING]

   일반

   --name value  저장소의 이름 (기본값: 자동 생성)
   --path value  저장소의 경로

```

{% endcode %}


---

# 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://data-programs.gitbook.io/singularity/kr/cli-reference/storage/create/opendrive.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.