| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
ci(github): start the Docker job from the documented .env as the runner user The job started the stack with a bare mkdir -p data && docker compose up -d. On a hosted runner that fails twice before any contract check runs: the runner account is not uid 1000, so the container (which Compose runs as the ids .env names, defaulting to 1000) cannot write the bind mount the runner just created and the entry point exits; and with no .env at all, every forwarded key interpolates to an empty string, so the check that a key from .env.docker.example reaches the container environment can only fail. Follow the guide's first-run sequence instead: copy the example .env, write the invoking user's ids into it, and start. SD_PORT is written into the same file so a local replay on a spare port publishes where the job polls. | 29 天前 |