fix(examples/service-fabric-cli): fix Dockerfile build

[vdice]

What does this change

• Fix for a build failure for this example bundle as seen in (unrelated PR) Updated references to debian:stretch with debian:stretch-slim #1387
• Once the above was fixed, we hit an issue wherein we hadn't pinned the json validator cli (ajv-cli) to a version and were hence pulling latest. There are breaking changes in the latest (perhaps we can look into this at a later date); for now, we pin to a known quantity (3.3.0)

What issue does it fix

N/A

Notes for the reviewer

N/A

Checklist

• Unit Tests
• Documentation
• Schema (porter.yaml)

[vdice]

Appear to be hitting #1389 (or a variant thereof)

Or maybe diff... this time the Win agent is stalled with:

"C:\windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "C:\a\_temp\0da71b6d-8267-41c0-8df3-0ab4d16302ef.cmd""
docker: error during connect: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.40/containers/create?name=registry: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.
See 'docker run --help'.

[carolynvs]

/azp run porter

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[carolynvs]

Docker crashed on the windows agent and didn't restart. For now I have deleted the unhealthy agent so that Azure will provision a new one. Later I'll look into preventing that from happening in the future.

[carolynvs]

Docker is configured to check for new versions I think. So it's hanging and preventing the docker service from starting. I'm going to see about fixing the agent image to not check for updates since it's so disruptive.

[carolynvs]

Pinning FTW! 🧷