DEV Community

David Haley
David Haley

Posted on • Edited on

Running a Vertex AI custom container

After creating our container, it's time to run it.

Our first container didn't work (of course). After a few iterations we got it running. 🎉

Vertex AI job list, 3 failed and 1 succeeded

After a container path whoopsie, the main challenge was fetching the active machine config from within the container.

Previously, we'd copy the notebook id into the benchmark then use the notebook API to fetch the machine config. We found the API to describe the custom job by ID which has the machine info … but you don't have an ID until the job is created. 🤨

This StackOverflow answer had the key. You do get to set a display name, then you can fetch all jobs filtered on that name.

So we'll need to make sure those job names (nominally for display) are actually unique identifiers…

Image of Timescale

🚀 pgai Vectorizer: SQLAlchemy and LiteLLM Make Vector Search Simple

We built pgai Vectorizer to simplify embedding management for AI applications—without needing a separate database or complex infrastructure. Since launch, developers have created over 3,000 vectorizers on Timescale Cloud, with many more self-hosted.

Read more

Top comments (0)

Image of Docusign

🛠️ Bring your solution into Docusign. Reach over 1.6M customers.

Docusign is now extensible. Overcome challenges with disconnected products and inaccessible data by bringing your solutions into Docusign and publishing to 1.6M customers in the App Center.

Learn more

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay