Local setup

Your computer differs from a pipeline in two ways that matter: licenses and access to images. Everything else you already know how to do.

Licenses

In a pipeline, the licenses your organization has purchased for Vector tools are served by a license server that your license-enabled runners can reach.

Locally, you provide your own licenses too, as a separate purchase from the vendor. The license servers the runners use are on an internal network and cannot be reached from your computer.

flowchart LR
      ci["Your pipelines"]:::green
      local["Your computer"]:::red
      ci -- "your licenses, served by the platform ✅" --> s
      local -- "you buy and provide your own ❌" --> s
      subgraph s ["licenses"]
            vl[Vector tools]
            ot[other tools]
            vl ~~~ ot
            click vl href "https://www.vector.com/us/en/company/get-info/licensing/" " "
      end
      classDef red stroke:#f00
      classDef green stroke:#0f0

Ask your Vector contact what applies to your setup. Licensing in full

If a pipeline fails with a license error, report it rather than working around it locally.

Reuse the container images

Pull the same images your pipelines use instead of building a toolchain from scratch, and you then debug the same environment the pipeline runs in.

docker login registry.code.vector.cloud
docker pull registry.code.vector.cloud/<your-organization>/registries/docker/<image>:<tag>

You need a personal access token for this; your sign-in session does not carry over to Docker. Registries and authentication

Behind a corporate proxy

If pulls or clones hang, or you get TLS errors that look like certificate problems, the usual cause is your company's proxy rather than anything on the platform.

What to allow, and how to test it