Installing on External Drive

[abhicmraja]

Hi. I use an M1 Mac, and I don't have enough storage space on my internal SSD to install Vivado. So I'm looking to get this installed on my external drive. I have setup Docker to use the external drive, but I realised that the .sh files in the repo still use the /home/user directory by default for the installation, and hence me getting the /home/user/Xilinx does not have enough space error even after allocating 100+GB to Docker on my external drive.

Is changing the "/home/user" to "/Volumes/" in all the .sh files the only way to go about this? Or is there any easier way to go about doing this? Would appreciate any help regarding this.

Thanks a lot in advance!

[ichi4096]

/home/user is a folder only visible inside the docker container. It doesn't have access to any files on the host system except to the folder You downloaded this repository to. This is because /home/user is mounted to that folder in one of the docker commands in the scripts.

I had no trouble installing onto an external SSD. What You can try to do when the setup asking You to log in:

• Don't type in Your credentials
• Open the Docker Desktop dashboard
• Select the running container
• Open the terminal (I don't know what the button or tab is called exactly)
• Type in "df -h"

This should tell You how much space the container thinks it has.

[abhicmraja]

I removed the file .config file, but I'm still getting the same results.

Just to make sure, Docker can stay on the internal drive. You put the repo on the external drive, and run the .sh file, and it should work. Is that all that has to be done? Am I missing something? Should I add my volume for file sharing? (By default /Volumes is there.)

Because whether I run the setup.sh file on my internal drive or on the external drive, the "/run/host_mark/Volumes" has only 229GB and 174GB has been used.

[ichi4096]

I was just about to describe how it worked for me, then I tested it again with the same code I knew had worked fine a few weeks ago and I get the same error... Now I can at least reproduce it.

I'll try to fix it, however, my suspicion is that it is an issue related to Docker or Rosetta 2 or maybe accurate disk space readings aren't even meant to be supported.

[abhicmraja]

Ohh ok. xD

Would installing it on my internal drive first (I'll free up the space) and then moving the container to my external drive be an easy process?

[ichi4096]

(Edit: Didn't see your new message. Your proposed method should work but there's an easier workaround described below.)

From what I can gather, if /Volumes is shared with the container, then mounts in the Linux containers of it and all of its subfolders report the free space of / in macOS. One workaround is to remove /Volumes and add /Volumes/AbhiAPFS or wherever your external drive is mounted to in macOS to the list of shared folders in Docker Desktop -> Settings -> Resources -> File sharing.

That should work for You for the time being. I'll add a notice in the readme.md or provide a fix later (I'm thinking of double-mounting the Volume in the user's home folder so that the data in question isn't under /Volumes exclusively anymore).

[abhicmraja]

Yep, I can confirm that removing /Volumes from Shared Folders works like a charm.

Thanks a lot for your help!

[ichi4096]

You're welcome :-)

[abhicmraja]

Just wanted to follow up....
The installation is complete (the Vivado folder is around 47GB), but one process got killed midway, and it's asking me to run cleanup.sh and redo the installation. Is there a way to "resume" the installation/verification?

The screenshot of the error:

[Edit]: When I say installation is complete, I meant that Vivado seems to be installed. During the full installation process I got an error

[ichi4096]

No clue what that could be. There is no "resume" function that I'm aware of.