Github workflows to utilize building on docker engine

[DieHard073055]

What would you like to be added:

Builds should use docker qemu + buildx.
Building on docker engine will allow us to utilize qemu.

Why is this needed:

To make the builds as OS agnostic as possible.

Reference Conversation

[defichain-bot]

@DieHard073055: Thanks for opening an issue, it is currently awaiting triage.

The triage/accepted label can be added by foundation members by writing /triage accepted in a comment.

Details

I am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

[defichain-bot]

@DieHard073055: There are no 'area' labels on this issue. Adding an appropriate label will greatly expedite the process for us. You can add as many area as you see fit. If you are unsure what to do you can ignore this!

You can add area labels by leaving a /area comment.

Details

I am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

[fuxingloh]

/area workflows
/triage accepted

[fuxingloh]

/area workflow

[fuxingloh]

/area packages
/package testcontainers
/priority important-soon

[fuxingloh]

/assign @mambisi can you help with this

[mambisi]

@fuxingloh cd.yml on this https://github.com/DeFiCh/metachain/blob/c0820458c0bad868dd36a495045ca24460cc5873/.github/workflows/cd.yml
already build with qemu buildx

[fuxingloh]

@fuxingloh cd.yml on this https://github.com/DeFiCh/metachain/blob/c0820458c0bad868dd36a495045ca24460cc5873/.github/workflows/cd.yml already build with qemu buildx

The setup and build are done on the GitHub workflow host instance via:

metachain/.github/workflows/release-docker.yml

Line 19 in cb6307d

runs-on: ubuntu-latest

with this build and run step:

metachain/.github/workflows/release-docker.yml

Lines 36 to 49 in cb6307d

	- name: Set up rust toolchain
	uses: actions-rs/toolchain@16499b5e05bf2e26879000db0c1d13f7e13fa3af # tag=v1.0.7
	with:
	profile: minimal
	toolchain: nightly
	target: wasm32-unknown-unknown
	default: true
	override: true
	- name: Cargo build
	uses: actions-rs/cargo@844f36862e911db73fe0815f00a4a2602c279505 # tag=v1.0.3
	with:
	command: build
	args: --release --all

the binary is then copied into a Docker Image via:

metachain/.github/workflows/release-docker.yml

Lines 51 to 54 in cb6307d

	- name: Save binary
	run: |
	mkdir -p build
	cp target/release/meta-node build/

and

metachain/Dockerfile

Lines 5 to 6 in cb6307d

	# Requires copy the binary to `build` folder beforehand
	COPY build/* /metachain

---

This issue was created to move the build process into Docker Engine with qemu and buildx. Since we're now building on host machine instead of a Docker multi-arch engine: https://www.docker.com/blog/multi-arch-images/

[mambisi]

okay got it

[fuxingloh]

okay got it

I'm not too familiar with Cargo build. Since for other languages, you need to build on the same OS/target to run on the same target arch/env. Or generally that's how it's done afaik

I will defer to you to make this decision, it might not warrant or require it. If you think otherwise just drop a note here with the explanation, I will close this issue.