gortium/compose
1
1
Fork 0
Code Issues Pull Requests 18 Actions Packages Projects Releases Wiki Activity

feat: update Hermes Dockerfile to build from forked source (gortium/hermes-agent) #20

Merged
gortium merged 1 commits from feat/hermes-fork-dockerfile into master 2026-05-11 02:07:42 +00:00
Conversation 0 Commits 1 Files Changed 3 +56 -48
Hermes commented 2026-05-10 21:55:44 +00:00
Collaborator
Copy Link

Summary

Update the AI stack to build the Hermes Docker image from our forked repo on Gitea instead of the official nousresearch/hermes-agent:latest base.

Changes

ai/compose.yml

  • Changed build: ./hermes to explicit build config with SSH agent forwarding

ai/hermes/Dockerfile

  • Clones from git@code.lazyworkhorse.net:gortium/hermes-agent.git at build time
  • Sets CHROME_EXECUTABLE env var so browser tool finds Playwright's Chromium
  • Removed patch_tts_tool.py step (Piper TTS default is now in fork source)
  • Keeps Piper TTS install + voice download

versioncontrol/compose.yml

  • Added GITEA__actions__ENABLED=true and DEFAULT_ACTIONS_URL=off for CI

Verification

cd /home/gortium/infra/assets/compose/ai
ssh-add ~/.ssh/id_ed25519
docker compose build hermes

Dependencies

  • Merge this PR first
  • Downstream: infra PR #35 (submodule pointer update)
## Summary Update the AI stack to build the Hermes Docker image from our forked repo on Gitea instead of the official `nousresearch/hermes-agent:latest` base. ## Changes ### ai/compose.yml - Changed `build: ./hermes` to explicit build config with SSH agent forwarding ### ai/hermes/Dockerfile - Clones from `git@code.lazyworkhorse.net:gortium/hermes-agent.git` at build time - Sets `CHROME_EXECUTABLE` env var so browser tool finds Playwright's Chromium - Removed `patch_tts_tool.py` step (Piper TTS default is now in fork source) - Keeps Piper TTS install + voice download ### versioncontrol/compose.yml - Added `GITEA__actions__ENABLED=true` and `DEFAULT_ACTIONS_URL=off` for CI ## Verification ```bash cd /home/gortium/infra/assets/compose/ai ssh-add ~/.ssh/id_ed25519 docker compose build hermes ``` ## Dependencies - **Merge this PR first** - Downstream: [infra PR #35](https://code.lazyworkhorse.net/gortium/infra/pulls/35) (submodule pointer update)
Hermes added 22 commits 2026-05-10 21:55:44 +00:00
feat: add custom ollama image with ROCm 6.1 + gfx906 support ef58155897 
- Add ollama/Dockerfile that builds ollama from source with AMDGPU_TARGETS=gfx906
- Uses ROCm 6.1 (rocm/dev-ubuntu-22.04:6.1.2-complete) for MI50 support
- Builds llama.cpp runner with HIPBLAS for gfx906 architecture
- Updates compose.yml to build from this Dockerfile instead of pulling ollama/ollama:latest
refactor: move hermes files into ai/hermes/ subdirectory d34a4d3647 
- ai/Dockerfile -> ai/hermes/Dockerfile
- ai/fix-permissions.sh -> ai/hermes/fix-permissions.sh
- ai/patch_tts_tool.py -> ai/hermes/patch_tts_tool.py
- ai/compose.yml: update hermes build context to ./hermes
- ollama stays at ai/ollama/Dockerfile
fix: update ollama Dockerfile to v0.23.2 with proper ROCm 6.1 + gfx906 build f023dc1ee4 
- Update OLLAMA_VERSION from v0.13.5 to v0.23.2
- Fix package: golang -> golang-go
- Add ENV HCC_AMDGPU_TARGET=gfx906 and HSA_ENABLE_SDMA=0
- Set proper ENTRYPOINT + CMD
fix: use ollama v0.23.2 native CMake build system for ROCm 6 + gfx906 c6d2f5918f 
The old Dockerfile used the deprecated llama.cpp/ subdirectory approach
which doesn't exist in ollama v0.23.2. Now using the official CMake
presets (ROCm 6 preset) with AMDGPU_TARGETS including gfx906:xnack-.
fix: add unzip dependency for ninja installation 956d76f14d
fix: set CMAKE_HIP_COMPILER explicitly for ROCm 6.1 HIP detection a3d0fa0072
fix: use CXX=hipcc legacy mode for HIP CMake build d8b77c97c3 
CMake 3.31 refuses CMAKE_HIP_COMPILER=hipcc with 'not supported'.
Using CXX=hipcc triggers the legacy HIP detection path which works.
fix: use ROCm amdclang++ as HIP compiler, keep GCC for CPU code 5b210fe624 
Setting CXX=hipcc caused compilation failures on CPU backends (AVX
intrinsics). Now using GCC for CPU, ROCm's amdclang++ for HIP only.
fix: remove unsupported AMDGPU_TARGETS (gfx1200) for ROCm 6.1 0c612d9731 
ROCm 6.1's AMD clang 17 doesn't support gfx1200 (RDNA4).
Use only targets supported by ROCm 6.1: gfx906, gfx908, gfx90a, gfx1030, gfx1100.
fix: correct AMDGPU_TARGETS to include gfx940/gfx1010/gfx1200 aa6bbe87bf 
Targets were corrupted during previous patch iterations, contained
gfx908/gfx90a from the CMake preset instead of gfx940/gfx1010/gfx1200.
fix: remove nonexistent CC=clang for Go build step f6bc2b07a7 
ROCm 6.1 image doesn't have clang/clang++ in PATH (only amdclang++).
GCC is the default and works fine for CGo linking.
fix: build CPU and HIP backends separately 0d87fb2556 
CPU backends compiled with GCC (fixes AVX intrinsic errors from hipcc).
HIP backend compiled with hipcc (legacy mode skips enable_language(HIP)).
Go binary built with GCC for CGo linking.
This avoids both CMAKE_HIP_COMPILER rejection and CXX=hipcc CPU failures.
fix: remove gfx1200 target (not supported by ROCm 6.1 clang 17) d52f18b0fa 
ROCm 6.1's AMD clang 17 doesn't recognize gfx1200 architecture
(introduced in ROCm 6.2+). Caused compilation failure on all .cu files.
fix: target only gfx906 for HIP compilation fc777e2de2 
gfx940/gfx1010/gfx1030/gfx1100 cause C++ narrowing errors in ollama's
mma.cuh with hipcc. Since we only have MI50 (gfx906) cards, compile
for gfx906 only. Reduces build time and avoids upstream code bugs.
fix: add /usr/local/go/bin to ROCm PATH (was overridden) 0f7b22c19b 
ENV PATH for ROCm overwrote the previous PATH that included Go.
Without Go in PATH, 'go build' fails with 'go: not found'.
fix: use ROCm 6 preset with HIP language detection for proper GPU kernel compilation 32df546550 
- Use --preset 'ROCm 6' for HIP build step (enables enable_language(HIP))
- Remove /opt/rocm from PATH for CPU build to prevent check_language(HIP)
- Add CMAKE_PREFIX_PATH=/opt/rocm so find_package(hip) finds hip-config.cmake
- cmake --install --component HIP now works correctly with OLLAMA_RUNNER_DIR=rocm
fix: pre-set CMAKE_HIP_COMPILER="" for CPU build to prevent HIP detection 208bfd4612
fix: use cmake -B to override preset binaryDir, cmake --build/--install use explicit path bf2f17c5e2
fix: copy /build/dist/lib/ollama/ (not /build/dist/lib/) to avoid extra nesting f31ae59717
fix: set CMAKE_INSTALL_PREFIX=/build/dist at configure time for CPU, match preset for HIP 9cc7edfb39
fix: add ldflags for version, remove privileged, enable flash attention 6b82a26c25
feat: update Hermes Dockerfile to build from forked source 46241d10c5 
- Switch Dockerfile to clone from gortium/hermes-agent (Gitea fork)
- Add SSH agent forwarding for private repo clone at build time
- Set CHROME_EXECUTABLE for Playwright Chromium
- Remove patch_tts_tool.py (Piper patch now in fork source)
- Enable Gitea Actions in versioncontrol compose
gortium merged commit 61a59dfac1 into master 2026-05-11 02:07:42 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Hermes gortium
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gortium/compose#20
No description provided.
Delete Branch "feat/hermes-fork-dockerfile"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?