Create working multistage Dockerfile

[jbowen93]

Description

Create a new Dockerfile that meets the expectations of both the docker-compose and k8s cluster setups.

This means that the entrypoint to the container is the binary itself (celestia-appd in this case) .

It is expected that the appropriate arguments are passed to the container as if one was running the binary locally. Configuration isn't baked into the image and is expected to be passed as flags or using volume mounts.

For examples see docker-compose and k8s.

This has been manually tested using the following instructions:

cd celestia-app && docker build -f docker/Dockerfile -t jbowen93/celestia-app:multi .
cd devops-test/devnet && sed -i 's/jbowen93\/celestia-app:devnet/jbowen93\/celestia-app:multi/g' docker/docker-compose.yml
docker-compose -f docker/docker-compose.yml up

as well as with the devops-test/devnet/k8s cluster

closes: #153

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against correct branch (see CONTRIBUTING.md)
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards.
• Wrote unit and integration tests
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added relevant godoc comments.
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer
• Review Codecov Report in the comment section below once CI passes

[Bidon15]

🚢
Awesome job! The devops-test compose file looks slick and sick!

[evan-forbes]

awesome utACK

[renaynay]

Since this Dockerfile is multi-stage and meets the requirements of k8s/compose setup, can we name it something ____.Dockerfile to indicate that this is its main use?

[jbowen93]

Since this Dockerfile is multi-stage and meets the requirements of k8s/compose setup, can we name it something ____.Dockerfile to indicate that this is its main use?

My intention was that this would be the canonical and ideally only Dockerfile needed for this repository. As such I believe we should use the "top level" Dockerfile naming.

[adlerjohn]

utACK