metasploit-framework
metasploit-framework copied to clipboard
rapid7
Dockerhub metasploit-framework releases are old
Steps to reproduce
As reported by @rasheed-rd in https://github.com/rapid7/metasploit-framework/pull/16812#issuecomment-1194304318 - the current dockerhub version of metasploit-framework 6.0.55 and the latest is released version is 6.2.8. The last update was almost a year ago.
It'd be great to have this docker build updating again, potentially weekly - aligning with our release process.
Hi!
This issue has been left open with no activity for a while now.
We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi!
This issue has been left open with no activity for a while now.
We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.
Hi!
This issue has been left open with no activity for a while now.
We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.
I was actually just looking at this today and I'd love to determine why this is occurring and how we can create a system to build these releases automatically and tag them appropriately. @adfoster-r7 would you be up for syncing up on this next week?
Hi!
This issue has been left open with no activity for a while now.
We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.
Bumping this up again, we really should look into resolving this at some point after Christmas break.
I believe @jmartin-r7 and I sync'd up on this previously, and there was a change on dockerhub's side that removed the auto build support that impacted this.
It didn't seem high priority at the time of reporting, as it doesn't seem like this impacts a lot of folk
