> For the complete documentation index, see [llms.txt](https://docs.vex-nx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vex-nx.com/labs/containerlab-passport.md).

# Containerlab Passport

![Import Lab entry (Containerlab path)](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FrHGPcA7Eaewk1nJGW4o2%2Fve20261112v5-import-lab.png?alt=media)

## Goal

Import a Containerlab topology YAML into VEX-NX, or export an existing lab as Containerlab YAML for interchange.

## Import

1. Open **Labs**
2. Choose **Import Containerlab** (or the Containerlab import action on the Labs page)
3. Select the `.yml` / `.yaml` file
4. Preview the mapped nodes / links when offered
5. Confirm create - open the new lab in Design and review templates / images

Expected: a lab whose topology matches the Containerlab graph as far as supported runtimes and image mappings allow. Unsupported kinds surface as clear import errors or placeholder notes.

## Export

1. Open the lab
2. Workspace **More** (or lab export menu) -> **Export Containerlab YAML**
3. Save the downloaded file

Use export for sharing a topology skeleton with Containerlab users. Guest disks and proprietary images are not redistributed - peers still need their own image files.

## Related

* [Import Lab](/labs/import-lab.md)
* [Migrate Lab](/labs/migrate-lab.md)
* [Features](/getting-started/features.md)


---

# 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.vex-nx.com/labs/containerlab-passport.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.