[Bump Docker] - V2.13.0

[0x7274]

Hi there @epi052 ,

in reference to #1270 can we please update the docker hub image epi052/feroxbuster:latest to latest V2.13.0
Currently still 2.12.0 😉

Thanks in advance!

[0x7274]

For anyone needing one, I pushed this v2.13.0 image in the meantime 0x7274/feroxbuster

IF you do not trust a stranger from the internet, build & push it yourself (replace <yourName>):

git clone https://github.com/epi052/feroxbuster.git

cd .\feroxbuster\

docker build -t epi052/feroxbuster:v2.13.0 .

docker tag epi052/feroxbuster:v2.13.0 <yourName>/feroxbuster:v2.13.0

docker push <yourName>/feroxbuster:v2.13.0

[epi052]

howdy!

as far as i can tell, the normal ci action to push/update docker ran on the same day 2.13.0 was released. i checked dockerhub and the last push from me happened on that date. The last github action related to docker looks good. There's nothing I can see that would make me think 2.13.0 isn't the version tagged as latest. However, i pulled the latest version and it is indeed reporting 2.12.0.

There's a version 2.13.0 in docker, but it's not tagged as latest.

I'm about to push 2.13.1, so hopefully this will fix itself on the next release.

[0x7274]

Ok that already sounds great, I only figured it out, that there must be a missmatch, as the tagged latest docker image still had bug #1270 on Windows - only found out testing my toolkit cross platform 😂

But let's be honest, that is affecting like probably less then 1% of the people that ever use feroxbuster to run it on windows xd
(and those know how to build and make their own docker image with the fixed version or find other solutions 😉)

Only wanted to highlight, as it might help you close/"solve" some issues of new features "not working/available" when using docker, as this still might affect a few more peeps 😊