# Node issue with old 32 bit VM

**URL:** <https://community.jenkins.io/t/node-issue-with-old-32-bit-vm/5187>\
**Category:** Using Jenkins\
**Tags:** question\
**Created:** [January 3, 2023, 2:25pm UTC](https://community.jenkins.io/t/node-issue-with-old-32-bit-vm/5187 "2023-01-03T14:25:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisMicro](https://avatars.discourse-cdn.com/v4/letter/c/df705f/32.png) [@chrisMicro](https://community.jenkins.io/u/chrisMicro)\
**Post date:** [January 3, 2023, 2:25pm UTC](https://community.jenkins.io/t/node-issue-with-old-32-bit-vm/5187/1 "2023-01-03T14:25:04Z")

</div>

I’m curious if there is a workaround for this old VM node that we rarely use here? The problem is that the old VM is 32 bit so it can only support JDK 1.8 and Jenkins no longer supports it. Just curious if there is a Jenkins solution to the issue?

---

<div class="post-metadata">

**Author:** ![PierreBtz](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/pierrebtz/32/55_2.png) [@PierreBtz](https://community.jenkins.io/u/PierreBtz)\
**Post date:** [January 3, 2023, 3:43pm UTC](https://community.jenkins.io/t/node-issue-with-old-32-bit-vm/5187/2 "2023-01-03T15:43:24Z")

</div>

You didn’t specify the OS the agent is running on but adoptium lists 32 bits compatible distribution at least for Windows: [https://adoptium.net/en-GB/temurin/releases/?version=11](https://adoptium.net/en-GB/temurin/releases/?version=11)

---

<div class="post-metadata">

**Author:** ![chrisMicro](https://avatars.discourse-cdn.com/v4/letter/c/df705f/32.png) [@chrisMicro](https://community.jenkins.io/u/chrisMicro)\
**Post date:** [January 3, 2023, 3:50pm UTC](https://community.jenkins.io/t/node-issue-with-old-32-bit-vm/5187/3 "2023-01-03T15:50:03Z")

</div>

Sorry, the OS is CentOS 5.10.

---

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [January 3, 2023, 8:10pm UTC](https://community.jenkins.io/t/node-issue-with-old-32-bit-vm/5187/4 "2023-01-03T20:10:37Z")

</div>

CentOS 5.10 is unsupported by the CentOS project. Jenkins does not support operating systems that are not supported by the operating system provider. See the [Linux support policy](https://www.jenkins.io/doc/administration/requirements/linux/#support-levels) for more details.

You could treat the CentOS 5.10 computer as though it were embedded hardware, perform the checkout on an agent, use `rsync` to copy the workspace from the agent to the CentOS 5.10 machine, use `ssh` on the agent to launch the build on CentOS 5.10 build, then use `rsync` to copy the workspace from the CentOS 5.10 machine back to the agent. That provides most of the benefits of the Jenkins job without requiring that you run an agent on the CentOS 5.10 computer.