Launch FAQ

  less than a minute  

Are there best practices for using Launch effectively?

Can I specify a Dockerfile and let W&B build a Docker image for me?

Can Launch automatically provision (and spin down) compute resources for me in the target environment?

Can you specify secrets for jobs/automations? For instance, an API key which you do not wish to be directly visible to users?

Does Launch support parallelization? How can I limit the resources consumed by a job?

How can admins restrict which users have modify access?

How do I control who can push to a queue?

How do I fix a "permission denied" error in Launch?

How do I make W&B Launch work with Tensorflow on GPU?

How does W&B Launch build images?

I do not like clicking- can I use Launch without going through the UI?

I do not want W&B to build a container for me, can I still use Launch?

Is `wandb launch -d` or `wandb job create image` uploading a whole docker artifact and not pulling from a registry?

What permissions does the agent require in Kubernetes?

What requirements does the accelerator base image have?

When multiple jobs in a Docker queue download the same artifact, is any caching used, or is it re-downloaded every run?


Last modified January 17, 2025: [DOCS-1130] Remove incorrect statement about view-only members and API keys (#1005) (2e841e5)