using forced rm instead of stopping the container first for redeploy... This was inspired by a descrepency between the point in time which information about @CurrentResource was generated and the current state. This could be avoided by checking every time someone calls running? instead of effectivly caching it at the begining of handleing the action