fdb268cee0
Files touched — docs/drivers/Modbus-Test-Fixture.md dropped the key-files pointer at deleted Pymodbus/ + flipped "primary launcher is Docker, native fallback retained" framing to "Docker is the only supported launch path" (matching the code). docs/v2/dev-environment.md dropped the "skips both Docker + native-binary paths" parenthetical from AB_SERVER_ENDPOINT + flipped the "Native fallbacks" subsection to a one-liner that says Docker is the only supported path. docs/v2/modbus-test-plan.md rewrote §Harness from "pip install pymodbus + serve.ps1" setup pattern to "docker compose --profile <…> up" + updated the §PR 43 status bullet to point at Docker/profiles/. docs/v2/test-data-sources.md §"CI fixture (task #180)" rewrote the AB CIP section from "LocateBinary() picks binary off PATH" + GitHub Actions zip-download step to "Docker is the only supported reproducible build path" + docker compose GitHub Actions step; dropped the pinned-version SHA256 table + lock-file reference because the Dockerfile's LIBPLCTAG_TAG build-arg is the new pin. Code docstrings + error messages — these are developer-facing operational text too. ModbusSimulatorFixture SkipReason strings (both branches) now point at `docker compose -f Docker/docker-compose.yml --profile standard up -d` instead of the deleted `Pymodbus\serve.ps1`; doc-comment at the top references Docker/docker-compose.yml. Snap7ServerFixture SkipReason strings + doc-comment point at Docker/docker-compose.yml instead of PythonSnap7/serve.ps1. S7_1500Profile.cs docstring updated. Modbus Dockerfile comment pointing at deleted tests/.../Pymodbus/README.md redirected to docs/drivers/Modbus-Test-Fixture.md. DL205Profile.cs + DL205StringQuirkTests.cs + S7_1500Profile.cs (in Modbus project) docstrings flipped from Pymodbus/*.json references to Docker/profiles/*.json. Left untouched deliberately: docs/v2/implementation/exit-gate-phase-2-closed.md — that's a historical as-of-2026-04-18 snapshot documenting what was skipped at Phase 2 closure; rewriting would lose the date-stamped context. Its "oitc/modbus-server Docker container not started" + "ab_server binary not on PATH" lines describe the fixture landscape that existed at close time, not current operational guidance. Final sweep confirms zero remaining `Pymodbus/` / `PythonSnap7/` / `LocateBinary` / `AbServerSeedTag` / `BuildCliArgs` / `AbServerPlcArg` mentions anywhere in tracked files outside that historical exit-gate doc. Whole-solution build still 0 errors. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
28 lines
1.1 KiB
Docker
28 lines
1.1 KiB
Docker
# pymodbus simulator container for the Modbus integration suite.
|
|
#
|
|
# Pinned base + package version so the fixture surface is reproducible —
|
|
# matches the version referenced in docs/drivers/Modbus-Test-Fixture.md.
|
|
FROM python:3.12-slim-bookworm
|
|
|
|
LABEL org.opencontainers.image.source="https://github.com/dohertj2/lmxopcua" \
|
|
org.opencontainers.image.description="pymodbus simulator for OtOpcUa Modbus driver integration tests"
|
|
|
|
RUN pip install --no-cache-dir "pymodbus[simulator]==3.13.0"
|
|
|
|
# Ship every profile in the image so one container can serve whichever
|
|
# family a test run needs; the compose file picks which JSON is active via
|
|
# the command override.
|
|
WORKDIR /fixtures
|
|
COPY profiles/ /fixtures/
|
|
|
|
EXPOSE 5020
|
|
|
|
# Default to the standard profile; docker-compose.yml overrides per service.
|
|
# --http_port intentionally omitted; pymodbus 3.13's web UI binds on a
|
|
# container-local default we don't publish, so it's not reachable from the
|
|
# host and costs nothing.
|
|
CMD ["pymodbus.simulator", \
|
|
"--modbus_server", "srv", \
|
|
"--modbus_device", "dev", \
|
|
"--json_file", "/fixtures/standard.json"]
|