gitea_admin/agent-builder
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

prompt: tell the inner loop about runtime.apt_packages
All checks were successful
build / build (push) Successful in 37s
Details

Browse Source 
So generated agents that need ffmpeg / imagemagick / etc. declare them
in a2a.yaml instead of failing at runtime with a missing binary.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
robert
2026-05-15 21:44:24 -03:00
parent 90b24e0064
commit a021239ef6
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
agent_builder/builder.py
View File

@@ -65,6 +65,19 @@ expose:
public: true public: true
``` ```
If the agent needs system binaries the Python-only base image doesn't
ship (ffmpeg, imagemagick, poppler-utils, sqlite3, etc.), declare
them under ``runtime.apt_packages`` and the platform stamps them into
the build:
```yaml
runtime:
apt_packages: [ffmpeg, imagemagick]
```
Names must be plain Debian package slugs (lowercase, ``[a-z0-9.+-]``).
Don't reach for this for Python deps — those go in ``requirements.txt``.
And a ``requirements.txt`` listing any extra deps beyond a2a-pack And a ``requirements.txt`` listing any extra deps beyond a2a-pack
itself (pandas, httpx, etc. — the base image ships a2a-pack already itself (pandas, httpx, etc. — the base image ships a2a-pack already
when you deploy through the control plane). when you deploy through the control plane).