This repository was archived by the owner on Feb 15, 2026. It is now read-only.
refactor: align build system with container-packaging-tools#44
Merged
Conversation
Simplify the build system to match the cleaner pattern used in container-packaging-tools, eliminating sources of CI failures. Changes: - Replace Dockerfile.debtools with Dockerfile.devtools (Bookworm base, non-root user, system-wide uv installation) - Replace docker-compose.debtools.yml with docker-compose.devtools.yml (remove env_file dependency, simplify volume mounts) - Simplify run script: remove _env, _export_unset, dev-env functions that caused CI failures with .env file handling - Rename debtools to devtools for consistency - Add docker-shell and docker-clean commands - Fix package-name in workflow: halpi2-daemon → halpid to match debian/control The old build system had multiple failure modes: 1. env_file requiring .env to exist 2. grep failing on comment-only .env files 3. Complex volume mounting with DIR_NAME variable 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Align the build system with the cleaner pattern used in container-packaging-tools, eliminating the sources of CI failures we've been debugging.
Changes
Docker Setup
Replace
Dockerfile.debtools→Dockerfile.devtoolsbuilderuseruvsystem-wide (not per-user)Replace
docker-compose.debtools.yml→docker-compose.devtools.ymlenv_file: ../.env(root cause of many CI issues)- ..:/workspace(no${DIR_NAME}complexity)Run Script
_env,_export_unset,dev-envfunctions (caused CI failures)debtools→devtoolsfor consistencybuild-deb: justuv sync && dpkg-buildpackagedocker-shellanddocker-cleancommandsbuildcommand as main entry pointWorkflow
package-name: halpi2-daemon→package-name: halpidto matchdebian/controlWhy This Fixes CI
The old build system had multiple failure modes:
env_file: ../.envrequired the file to existgrep -v '^#'returned exit code 1 on comment-only files${DIR_NAME}variable handling in volume mountsThe new system has none of these issues - it's the same pattern that works reliably in container-packaging-tools.
Test plan
🤖 Generated with Claude Code