Create repository official Dockerfile

[rach-id]

This PR simplifies the main Dockerfile for Celestia-app.
It creates an image containing the Celestia-app binary and doesn't take into account the other development related to it. For example, under docker/ directory, we had a Dockerfile that was shaped to suite the ephemeral cluster needs. However, when tagged using GitHub actions, it was acting as the main Celestia-app docker image. Thus, if someone wants to use that image, they will have to follow a complex way of specifying the home directory and existing files. In the meanwhile, the official repository Dockerfile shouldn't be as opinionated as possible.

Also, I renamed docker/Dockerfile to docker/Dockerfile_ephemeral in case we need to keep that image for the ephemeral cluster. However, I suggest we add a new GitHub action that creates that image and tags it with a tag that reflect that it will be used for the ephemeral cluster, example : ghcr.io/celestiaorg/celestia-app-ephemeral:latest (Let me know if we want to add that action so that I add it to this PR).

This comes from the need of having a base Celestia-app docker image that will be built during integration tests.

[rach-id]

The issue with this approach is priv_validator_state.json:

ERR CONSENSUS FAILURE!!! err="rename /opt/data/write-file-atomic-08895712196458512116 /opt/data/priv_validator_state.json: device or resource busy" module=consensus s
tack="goroutine 216 [running]:\nruntime/debug.Stack()\n\t/usr/local/go/src/runtime/debug/stack.go:24 +0x65\ngit.luolix.top/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\n\t/go/
pkg/mod/github.com/celestiaorg/celestia-core@v1.0.1-tm-v0.34.16/consensus/state.go:726 +0x4c\npanic({0x1978200, 0xc0022989c0})\n\t/usr/local/go/src/runtime/panic.go:1038 +0x215\ngit.luolix.top/t
endermint/tendermint/privval.(*FilePVLastSignState).Save(0x78)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.0.1-tm-v0.34.16/privval/file.go:139 +0x90\ngit.luolix.top/tendermint/tenderm
int/privval.(*FilePV).saveSigned(0xc0000fc600, 0xc0027bb700, 0x4106b4, 0x0, {0xc0027c0280, 0x80, 0x203000}, {0xc0022ac700, 0x40, 0x40})\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1
.0.1-tm-v0.34.16/privval/file.go:395 +0x88\ngit.luolix.top/tendermint/tendermint/privval.(*FilePV).signProposal(0xc008daec80, {0xc00906ded7, 0x7}, 0xc0000fc680)\n\t/go/pkg/mod/github.com/celesti
aorg/celestia-core@v1.0.1-tm-v0.34.16/privval/file.go:381 +0x2ba\ngit.luolix.top/tendermint/tendermint/privval.(*FilePV).SignProposal(0xc0000fc600, {0xc00906ded7, 0x0}, 0x0)\n\t/go/pkg/mod/githu
b.com/celestiaorg/celestia-core@v1.0.1-tm-v0.34.16/privval/file.go:265 +0x1e\ngit.luolix.top/tendermint/tendermint/consensus.(*State).defaultDecideProposal(0xc009272700, 0x1, 0x0)\n\t/go/pkg/mod
/github.com/celestiaorg/celestia-core@v1.0.1-tm-v0.34.16/consensus/state.go:1132 +0x2e2\ngit.luolix.top/tendermint/tendermint/consensus.(*State).enterPropose(0xc009272700, 0x1, 0x0)\n\t/go/pkg/m
od/github.com/celestiaorg/celestia-core@v1.0.1-tm-v0.34.16/consensus/state.go:1096 +0x6a3\ngit.luolix.top/tendermint/tendermint/consensus.(*State).enterNewRound(0xc009272700, 0x1, 0x0)\n\t/go/pk
g/mod/github.com/celestiaorg/celestia-core@v1.0.1-tm-v0.34.16/consensus/state.go:1019 +0xa67\ngit.luolix.top/tendermint/tendermint/consensus.(*State).handleTimeout(0xc009272700, {0xc000d923f0, 0
xc000d923f0, 0xd923f0, 0xc0}, {0x1, 0x0, 0x1, {0x181e0134, 0xeda15924b, ...}, ...})\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.0.1-tm-v0.34.16/consensus/state.go:892 +0x4a5\ngith
ub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0xc009272700, 0x0)\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.0.1-tm-v0.34.16/consensus/state.go:791 +0x6bf\ncreate
d by github.com/tendermint/tendermint/consensus.(*State).OnStart\n\t/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.0.1-tm-v0.34.16/consensus/state.go:378 +0x12f\n"

Even when mounted with the correct permissions, it still panics. Thus, forcing users to either:

• Run a custom script when starting the container. This means we should change entrypoint to cmd
• Or, create a new image which creates that file somewhere.

Will keep on investigating this.

[rach-id]

The current way the above problem is solved is via adding a custom script that creates the priv_validator_state.json file in case we're executing the start command and the file doesn't exist.
This can be a temporary solution until we investigate the above logs more.

[Bidon15]

Noice. I think creating an action for epheremal cluster makes sense and will be cool if this can be done within this PR
Afterwards, we can edit the path in ephemeral-cluster repo to reflect latest changes made in this PR

Passing to @jbowen93 if he is ok with this approach

[Bidon15]

Final say to @jbowen93

[rach-id]

@Bidon15 Awesome. Will add the GitHub action for ephemeral cluster if Josh agrees to these changes and think they make sense.

[adlerjohn]

Is this ready for review?

[rach-id]

@adlerjohn Waiting for Josh input to see whether to add a github action to this PR for the ephemeral cluster docker image or not.

[jbowen93]

Apologies for the delay in review. Left some comments. I'm fine adding a gh action for ephemeral to a later PR.

[jbowen93]

Resolved comments and approved