@wenyongh
I am thinking that maybe we should remove ci/Dockerfile and always recommand .devcontainer/Dockerfile.

@wenyongh I am thinking that maybe we should remove ci/Dockerfile and always recommand .devcontainer/Dockerfile.

Yes, if possible, more docker files make more confusing and result in more maintain burden.

@wenyongh We still lefts some software versions relatied warnings. Should we indiciate versions of all dependencies? Or keep using latest ones?

@wenyongh We still lefts some software versions relatied warnings. Should we indiciate versions of all dependencies? Or keep using latest ones?

Not sure, shall we use the latest ones by default, and add some comments to indicate which versions to use if the os is not the latest?

@TianlongLiang

• please remove ci/Dockerfile, and recommaned vscode development container in documents.
• please make sure that all references to ci/Dockerfile are handled.

OK, I will get to it.

@wenyongh We still lefts some software versions relatied warnings. Should we indiciate versions of all dependencies? Or keep using latest ones?

Not sure, shall we use the latest ones by default, and add some comments to indicate which versions to use if the os is not the latest?

IIUC,

• apt-get install will install the package with the latest available version. For example, there is a chance that apt-get will install difference version on Ubuntu 20.04 and Ubuntu 22.04. It depends on which version the package owner uploaded. Usually it dosn't matter since apt-get is so popular that any package problem will be fixed ASAP.
• pip install is the same story

@TianlongLiang

• please remove ci/Dockerfile, and recommaned vscode development container in documents.
• please make sure that all references to ci/Dockerfile are handled.

so for the shell scripts in sample/workload/* and shell script in ci/, I should change the directory of Dockerfile to the one under .devcontainer, right?

@TianlongLiang

• please remove ci/Dockerfile, and recommaned vscode development container in documents.
• please make sure that all references to ci/Dockerfile are handled.

so for the shell scripts in sample/workload/* and shell script in ci/, I should change the directory of Dockerfile to the one under .devcontainer, right?

YES. that is the plan. let's see how it goes.

Now I finished modifying the shell scripts ci/build_wamr.sh and samples/workload/docker/build_workload.sh to redirect them to use .devcontainer/Dockerfile, and they ran successfully. And I used this Dockerfile in the vscode, which was also fined.

Also, I tested all the other Dockerfile and can successfully build them except product-mini/platforms/zephyr/simple/Dockerfile. It displays the following error messages when trying to build it even on the original unmodified Dockerfile:

Step 15/18 : RUN west espressif install
 ---> Running in 0e69b119aa3a
usage: west espressif [-h] [-b BAUD] [-p PORT] [-e ELF] {monitor}
west espressif: error: argument command: invalid choice: 'install' (choose from 'monitor')
The command '/bin/sh -c west espressif install' returned a non-zero code: 2

I tried to fix this issue today but so far no luck, I wonder if someone is more familiar with this west command or this zephyr platform that I could ask for help with. Meanwhile, I will continue to work on trying to fix this error