bloodhound.Dockerfile needs to point to SpecterOps org to find *hound releases #1057
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.
Description
Describe your changes in detail
Motivation and Context
https://specterops.atlassian.net/browse/BED-5259
https://github.com/SpecterOps/BloodHound/actions/runs/12675096237/job/35325322552
Build error on publish:
[linux/amd64 hound-builder 2/14] WORKDIR /tmp/sharphound
ERROR: failed to copy: httpReadSeeker: failed open: unexpected status code : 403 Forbidden
This looks to be an issue of the Dockerfile looking to the old BloodHoundAD org for Sharphound and Azurehound releases, while they now exist in SpecterOps org.
How Has This Been Tested?
Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to
see how your change affects other areas of the code, etc.
Screenshots (optional):
Types of changes
Checklist: