build: docker releases and compose file

[walkah]

Review Type Requested (choose one):

• Glance - superficial check (from domain experts)
• Logic - thorough check (from everybody doing review)

Summary

Provide a one line summary and link to any relevant references

Task/Issue reference

Re: #89

Details (optional)

• Adds a docker-compose file for development
• Publishes all docker containers to Github container registry

How to test this code? (optional)

Run the following:

• ./stack compose-init
• ./stack compose-up

[AquiGorka]

First time I ran ./stack compose-init I got the following:

WARN[0000] The "DOPPLER_TOKEN_SOLVER" variable is not set. Defaulting to a blank string. 
WARN[0000] The "DOPPLER_TOKEN_JOB_CREATOR" variable is not set. Defaulting to a blank string. 

I see it is being set at compose-up time, not really know how to offer a solution, just bringing it to your attention.

[AquiGorka]

First time I ran ./stack compose-up

[walkah]

First time I ran ./stack compose-up

Oh interesting. Looks like building the docker images took longer than the doppler secret 1m timeout. Good to know! I'm new to doppler - any issue bumping that to 10m or something? Or I can add a separate build step...

[walkah]

I see it is being set at compose-up time, not really know how to offer a solution, just bringing it to your attention.

harmless warning, but yeah, it's scary. I can make it go away :)

[AquiGorka]

Oh interesting. Looks like building the docker images took longer than the doppler secret 1m timeout. Good to know! I'm new to doppler - any issue bumping that to 10m or something? Or I can add a separate build step...

Let's up the time for those tokens yeah.

[AquiGorka]

On the second run, this time the resource-provider errored because it could not find the solver.
Is there a way to set order of execution and some spare time? Both the job-creator and resource-provider need the solver to have connected to the chain and registered itself.

[AquiGorka]

🍬 🍬 (sweet!)

On the 3rd run all services were up and ready, I ran a cli job, an onchain job and the integration tests and all worked correctly! 🎉
I did leave a comment in regards to make the results from onchain available to the host - maybe, your call if the intention here does not need to make them available as this may be intended for testing purposes.

[walkah]

Okay, @bgins & @AquiGorka - I've made a bunch of updates based on your feedback, including:

• adding healthhecks and restarts to make sure services all get started correctly on first boot
• bumped the timeout on the doppler tokens for fresh initial docker build
• updated the mountpoint for the rp/bacalhau image so results are accessible in ./data/bacalhau
• I also added ./stack compose-build (to build fresh images if you're making local changes) and ./stack compose-down to clean up

Thanks for all the feedback! 🙏