Fix: "Secure microservices with Kong and Ory" docker-compose.yml issues #34
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.
Fixed a couple of issues with
kratos-oathkeeper-kong
example.kong:latest
breakskratos-oathkeeper-kong
example by having thekong
containers exit. Now pinned tokong:2.7.2
which probably was latest when you coded the example seems to work. The relevant container logs:The same complaint comes up with the
platform: linux/arm64
directive and was removed fromdocker-compose.yml
.hello
microservice image did not contain a binary as it failed to build due to missingCGO_ENABLED=0
build directive.Related Issue or Design Document
The PR concerns a fix to the code linked to by the Secure microservices with Kong and Ory tutorial.
The relevant GitHub issue is #33.
Checklist
vulnerability, I confirm that I got green light (please contact security@ory.sh) from the
maintainers to push the changes.
Further comments
Docker image pinning is probably a safe practice.