build(docker): add dockerize image

[alekseyolg]

The Dockerezer image currently on the Helm Chart is too old and has critical vulnerabilities, for example:

busybox, 1.26.2-r5, CVE-2017-16544 (https://nvd.nist.gov/vuln/detail/CVE-2017-16544)

This pr is designed to solve this problem

SUMMARY

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[alekseyolg]

Hi all!
I can not understand the reason for the error when running the test:

Python Misc / pre-commit (3.9) (pull_request) 

Maybe someone can advise?

[craig-rueda]

Do we need this? I think it's preferable to just switch over to the "official" image. Or I wonder if we could use busybox or something? 🤔

[alekseyolg]

@craig-rueda I don't understand what you mean by "official". I found only this repository on dockerhub (on the attached image). The youngest image from there is 4 years old. If I did not find a link to some official image, then I would be grateful if you show it to me, and I, in turn, could study this issue.

About the busybox image: dockereze requires openssl to work, and busybox doesn't have a package manager to install it, so in my opinion the best way is to use the alpine base image.

[craig-rueda]

Ok, makes sense. I wasn't sure what we were using that image for in the first place 😄 . I see what's going on here - you're moving us to "official" (apache) ;)

[alekseyolg]

We need this image in order to expect connection to postgreSQL and Redis. If you do not use this image, then users may make an error when starting the chart and will endlessly receive a crashloopbackoff, and this image in the work logs clearly shows that the connection failed and repeats attempts to contact the destination (in my opinion, this is a good idea ).

[craig-rueda]

Looks like CI is failing, otherwise LGTM

[alekseyolg]

@craig-rueda I managed to solve the problem - now all processes work correctly!