Create Development Docker Container

[chatton]

Summary

Create and maintain a development container with all of the required tooling to work within the ibc-go repo, in order to provide a uniform experience for all developers.

Problem Definition

It can be a problem when working with different versions of tooling on a day to day basis but especially when onboarding onto the repo, as well as discrepancies in CI environments.

Proposal

Create a docker container which has tooling installed at specified versions which can be used in CI and our Makefiles. Some examples of software that could be included would be things such as.

• go
• goimports
• gofumpt
• npm
• hermes
• go relayer

This would allow a consistent development experience, as well as making onboarding onto the repo as painless as possible, wth the only project dependency required to get started being docker.

Makefile targets can utilize this dev container so everybody's experience is the same.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged/assigned

[Anmol1696]

This does make sense, but my concern would be with having hermes and go relayer as well into all the docker image. What are your thoughts on having 2 or 3 kinds of docker images:

• cosmos/ibc-go:<version>-dev: Can be larger in size, can have everything needed for development by a developer locally
• cosmos/ibc-go:<version>-build: Image with go, goimports, gofumpt, used for building code, running tests and used in the CI
• cosmos/ibc-go:<version>-linter: For CI specific dependencies, this can be lighter, can be more as per the requirements

CI docker images in my opion should be different from the development environment docker images, since on CI one would be more resource constrained. Same goes for builder images.

Although I do feel these docker images with work best if we layer up properly, as well as have a dependencies clear between them.

[Anmol1696]

@chatton I can raise an initial PR with the dev requirements as you mentioned.
Can have futher descissions from using the dev docker container itself and going from there.

[chatton]

Hi @Anmol1696, I think it could be work quite well to have separate containers like you suggested. To me the most important thing is a consistency among dev environments, an environment the same as CI is an added bonus (a lighter version for CI would be great too).

Would be happy to continue the conversation from an initial PR ❤️

[chatton]

I will also link this issue #1748 as it seems to be attempting to achieve a similar thing
cc @Anmol1696