WorldModels icon indicating copy to clipboard operation
WorldModels copied to clipboard

Docker Image Build Not Successful

Open miknad2319 opened this issue 2 years ago • 1 comments

Using macOS Monterey (12.3.1) M1 Pro

Running the following command inside the cloned repo directory on my local machine:

docker image build -t wm:1.0 -f docker/Dockerfile.wm .

results in the following error message:

Screen Shot 2023-06-22 at 2 16 59 PM

I fixed this by adding the command < --allow-authenticated > on line 21 of Dockerfile.wm after the < --no-install-recommends > command (following the -y flag)

In addition, I ran into problems with the command:

< RUN python3 -m pip install --no-cache-dir ${TF_PACKAGE}${TF_PACKAGE_VERSION:+==${TF_PACKAGE_VERSION}} >

The error prompt suggests I might need to run:

< apt-get install -y python3-dev >

on Ubuntu systems.

Screen Shot 2023-06-22 at 3 54 43 PM

This line is actually located towards the bottom (line ~94) but moving it up before the TensorFlow download line seems to do the trick

Upon including the python3-dev install above the TF download, the command line hangs for a long time but it should result in success

Also, the < apt -y update > command on line 93 failed for me because the package manager was missing a public key for the NVIDIA download (super technical, I know, but I've had a long day, forgive me), giving the following error:

< the following signatures couldn't be verified because the public key is not available >

I fixed this by prepending the "install packages" section with a line to update the package manager with the missing public key given by the error message, as per this resource here:

https://chrisjean.com/fix-apt-get-update-the-following-signatures-couldnt-be-verified-because-the-public-key-is-not-available/

This also took a long while. But in the end, the building of this docker image completed successfully!

Now to run the programs themselves...

miknad2319 avatar Jun 22 '23 23:06 miknad2319

@miknad2319 Thank you for sharing your knowledge! I encountered a similar error and tried to fix it here and run it, but could not Build. if possible, could you please tell me what is in the Dockerfile.wm?

kurikinton105 avatar Oct 16 '23 06:10 kurikinton105