Wes Floyd

@philwinder @lukemarsden @enricorotundo for FYI (@aronchick apologies for opening this bug a bit late!)

Based on our last conversations, it sounds like the OceanDAO folks can accommodate our current architecture and don't require k8s. Otherwise I hoped to use this direction as a shortcut...

Adding two use cases for K8s interfaces from the internal PL "Data Team" ([full notes here](https://docs.google.com/document/d/1REL-C0WgbWzv_xd3DTJwpzc90stiUByTJzooFvUYV9c/edit?usp=sharing)): 1) [Lily (Filecoin Network Indexing) orchestration with Argo](https://github.com/kasteph/lily-shed/blob/feat/argo/argo/repo.yaml) 2) Data Warehouse workloads via Spark...

+1 If we can implement long running containers (such as for web serving), this would open a wide range of use cases (and users) for Bacalhau.

Like all the ideas shared so far. My personal preference is for the most verbose/explicit flags initially (--command , --input-volume), then building auto-detection and shortcuts over time based on the...

Sharing an update that this feature will also be helpful for our partners LabDAO. Goal: the request is for a way to pipe the stdout/stderr logs to a logging service...

Asking this question to an LLM provided better guidance, so perhaps it should be included in the core SDK docs? > Including specific tool usage instructions in the system prompt...

This error occurs for me also, but only under the `develop` branch, not `main`

Perhaps this small PR would fix the branch for us? https://github.com/elizaOS/eliza/pull/2330 Or should this be fixed in the ci-cd for this branch 🤔 ?