# Novel Issues: Quick Porting of PYNQ using Pre-built images **URL:** \ **Category:** Support\ **Created:** [May 13, 2022, 4:16am UTC](https://discuss.pynq.io/t/novel-issues-quick-porting-of-pynq-using-pre-built-images/4187 "2022-05-13T04:16:58Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![briansune](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/briansune/32/3087_2.png) [@briansune](https://discuss.pynq.io/u/briansune)\ **Post date:** [May 14, 2022, 1:15pm UTC](https://discuss.pynq.io/t/novel-issues-quick-porting-of-pynq-using-pre-built-images/4187/3 "2022-05-14T13:15:26Z")
In case toy need to setup the environment to build any image under 2.7 revision: I enclosed a full details on setting up the env: > [@Stuck at extract yocoto](https://discuss.pynq.io/t/stuck-at-extract-yocoto/4134/8): > > Unless people having hard time on setting up the environment: Vagrant is not a good method to setup the SD build environment. I have not investigate to the bottom but what previous engineer shows there might Virtual R/W issue during such setup. STEPS: I will suggest download 18.04.06 LTS Ubuntu from official website Create a virtual disk size about 200GB or more, set the CPU \>#4, RAM \>#8192 Update Ubuntu packages before setting up the PYNQ 3b) Git clone the PYNQ to /home//PYNQ 3c) sudo ch… Don’t try Vagrant as it can result so many variations on different PC and hard drive right etc. --- _[View the full topic](https://discuss.pynq.io/t/novel-issues-quick-porting-of-pynq-using-pre-built-images/4187)._