One issue maybe about docker

[Billxgy]

Hi, when I try to run your project via running scripts in the terminal, there are some error infos, you may check my script file(in the following), nearly all of scripts are copied from your Readme file. By the way, my pc is MacBook Air.

Error information details:

Error response from daemon: No such [container:] 3dscan
docker: invalid reference format: repository name must be lowercase.
See 'docker run --help'.
Error response from daemon: No such container: 3dscan
Error response from daemon: No such container: 3dscan
Error response from daemon: No such container: 3dscan
Error response from daemon: No such container: 3dscan
Error response from daemon: No such container: 3dscan
Error response from daemon: No such container: 3dscan
Error response from daemon: No such container: 3dscan

script file:

workspace /Users/bill/Desktop/run
mkdir -p $workspace cd $workspace
git clone https://github.com/OSUSecLab/3DScan
wet "https://github.com/OSUSecLab/3DScan/releases/download/dependents/AssetStudio.executable.zip" wet "https://github.com/OSUSecLab/3DScan/releases/download/dependents/wine.drive.zip" wget "https: //github.com/OSUSecLab/3DScan/releases/down load/dependents/wine. source.zip" unzip AssetStudio.executable.zip unzip wine.drive.zip unzip wine.source.zip
docker rm -f 3dscan
docker run -d -v $workspace: /3DSCANWorkSpace -v $workspace/.wine:/root/.wine -e PATH=/3DSCANWorkSpace/wine-source: $PATH
--name 3dscan ubuntu tail -f /dev/null
docker exec 3dscan root: root -R /3DSCANWorkSpace/.wine docker exec 3dscan apt update
docker exec 3dscan apt install -y gcc make wet zlib1g-dev
docker exec 3dscan wet https://download.sourceforge.net/libpng/libpng-1.5.13.tar.g
docker exec 3dscan tar -xf libpng-1.5.13.tar.g
docker exec 3dscan bash -c "cd libpng-1.5.13; ./configure; make; make install" docker exec 3dscan In -s /usr/local/lib/libpng15.so.15 /usr/lib/×86_64-linux-gnu/libpng15.so. 15

[Billxgy]

@cszuo @chaowangsec

[cszuo]

Hi @Billxgy, thank you for letting us know. We will fix it, please stay tuned.

[Billxgy]

Hi @Billxgy, thank you for letting us know. We will fix it, please stay tuned.

Hi, zuo:
I am happy to inform you that the previous errors have been resolved. Now I have successfully created the container: 3dscan.
There are two improvements I have made:

1. Skip Docker rm - f 3dscan (if I didn't have the container, this command would generate a not found error)
2. for line: docker run -d -v $workspace: ......, let all characters in this line be lowercase (possibly due to PATH format requirements).

However, when running the Docker commands after the line:docker run -d -v $workspace: ......, some new error messages appeared(as shown below). It seems strange. If the previous error was due to different OS having different tolerance for instruction formats, then after entering the Docker container, I simulated the same environment as you. Why did these errors occur.
Anyway, I hope you can help me solve the problem. Thanks a lot. By the way, considering that many users like me are not proficient at using Docker, do you recommend that we directly use a PC with the Ubuntu OS to run the project? If you think this is feasible, you may add relevant instructions in the Readme file for us to refer.
docker指令报错信息.txt

Finally, thanks for your assistance. I sincerely hope that we can work together to make this project help more people.

[cszuo]

Hi @Billxgy , thank you for sharing the corrections you have made. For the first one, it was added in case the user runs the command several times which could already create a docker image 3dscan. Deleting it before other commands makes sure the user is starting from a clean env. The second correction looks interesting to me, I don't have to use lowercase. Could you share the error if you don't change it to lowercase?

Regarding the Docker error you encountered, it looks like you are running the docker in ARM based machine:

uname -m = aarch64
uname -r = 6.3.13-linuxkit
uname -s = Linux
uname -v = #1 SMP PREEMPT Thu Sep  7 07:48:47 UTC 2023

The env I am using is x86 based Ubuntu 22.04. It is using some pre-compiled binaries such as wine64. I would recommend you to try on a x86 machine or a VM. If you have to run it in ARM based machine, you will need to recompile the wine64 following the official doc.