Repository navigation
Mac: build trees in Docker volumes, a fixed Compose project name, Colima and M4 Pro RTF docs - #42
Merged
Merged
Conversation
Compose names a project after the compose file's directory, docker, so it adopted another checkout's stopped containers whose compose file also sits in a docker/ directory and has a ros service, and docker_stack.sh's `up --force-recreate` deleted one of them to create golem_ros. A fixed `name: golem` keeps the stack to its own containers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every file a container writes to the bind-mounted checkout reaches the macOS host, and on a university-managed Mac its endpoint security scans each one: under Colima on an M4 Pro a write took ~180 ms, against microseconds on the VM's disk, and a cold core_ws build ran over 40 min at 15% CPU without finishing. core_ws's build, install and log and the sim's msgs_ws now live in named volumes on the VM's disk; the sources stay bind-mounted. A cold build and stack start now takes 2.5 min. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MAC.md's image notes and CLAUDE.md's platform summary say the colcon build trees are Docker volumes on the Mac, why (per-file scanning of writes to the shared checkout on managed Macs) and how to clear them for a clean build. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GOLEM's Mac stack builds and runs under Colima (vz VM): an M4 Pro held the G1's g1_mac_sim at RTF 1.00. Colima shares only the home folder with its VM, so the checkout must sit under ~, and its default 30 GB disk is too small for the images. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The G1 RoboCasa sim alone and with g1_mac_sim, paced at real time, with the lidar and the head camera each on and off and the real MID-360's 20,000 points; and the sim alone unpaced over three runs each. Every combination holds real time with the sim loop idle about half the time. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
maxconwa
approved these changes
Nov 21, 2026
maxconwa
left a comment
Contributor
There was a problem hiding this comment.
Touches documentation, and docker-compose.mac.yaml. change to x86 docker-compose.yml only adds a name field.
Approved
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For Max: findings from bringing the Mac stack up on a university-managed MacBook Pro (M4 Pro, Colima). Five small commits, one concern each.
What changed and why
docker: fix the Compose project name to golem(affects every platform). Compose names a project after its directory,docker, so it adopted another checkout's stopped container (ahams_roswhose compose file also sat in adocker/folder with arosservice), anddocker_stack.sh'sup --force-recreatedeleted it to creategolem_ros. A fixedname: golemlimits the stack to its own containers. Nothing in the scripts or tests depended on the old project name.docker/mac: keep the colcon build trees in Docker volumes. On a managed Mac, endpoint security scans every file a container writes through the VM's file sharing. Writing 500 small files to the bind-mounted checkout took 89 s, against 0.02 s on the VM's own disk. A coldcore_wsbuild ran over 40 min at ~15% CPU without finishing.core_ws/{build,install,log}and the sim'smsgs_wsnow live in named volumes (golem_core_*,golem_msgs_ws), and the sources stay bind-mounted. A cold build plus stack start now takes 2.5 min. Suggested as good practice, since most of our laptops are university-managed now.docs: the Mac's build volumes: MAC.md's image notes and the CLAUDE.md platform summary, including how to clear the volumes for a clean build.docs: Colima as a Mac Docker runtime: Colima works. Its share covers only~, so the checkout must live there, and its default 30 GB disk is too small.docs: the Mac's real-time factor by sensor, on an M4 Pro: the G1 sim alone and withg1_mac_sim, with lidar and camera each on and off, plus the real sensor's 20k points. Every combination holds RTF 1.00 with the sim loop idle about half the time. Unpaced, the physics alone runs at 4-6× real time.Testing
docker_build.sh(all three arm64 images), thendocker_stack.sh up robocasa --g1. The band released, HOMIE stood, and there was no fall or estop across 14 stack and sim runs.docker compose configmounts the volumes and that the base file'smsgs_wsbind is replaced.python3 -m unittest tests.docker.test_workflows tests.docker.test_launch_ros_cacheon macOS: the same 16 failures before and after the change. They are environmental (noflockand other Linux tools), so they need a run on Linux.Existing checkouts: after this lands, the
golem_*containers belong to projectgolem. Old ones made under projectdockerare still removed by name by the wrappers. Oldcore_ws/build,installandlogfolders in a Mac checkout are no longer used and can be deleted.🤖 Generated with Claude Code