Skip to content
Epiglossary

Linux containers in Epicor Cloud

Kinetic

Starting with the 2025.2 release, Epicor began moving Epicor Cloud environments from Windows containers to Linux containers. Pilot environments moved first, from early 2026, with production environments following region by region. Kinetic itself looks the same to users, but anything that depended on the server being Windows can break: file paths, some custom code, report styles and a few URLs.

This page is for cloud administrators preparing for, or cleaning up after, the move. On-premises installations are not affected.

Which one am I on?

Section titled “Which one am I on?”

Open the environment’s tenant instance in the Cloud Management Portal. The Host OS field on the Summary tab shows Windows or Linux. Check Pilot and Live separately: during the migration they are often on different platforms, which is why something can work in Live and fail in Pilot.

What changes

Section titled “What changes”
Area What to expect
File paths Windows UNC paths don’t work. File shares are mounted at /epi/fs and /epi/ftp, and code should use FilePath and ServerFolder. See File shares and Linux paths.
Custom code BPMs and functions that use Windows-only .NET features, or that fail compilation checks, may be disabled or stop working.
SSRS report styles Long report style names can push the internal report path over its length limit. Copying styles and previewing reports have had permission and data source errors.
URLs and proxies Environment URLs and the proxies in front of them changed for some tenants. Hard-coded URLs in integrations, REST clients and shortcuts may need updating.
MES The data collection mode URL didn’t route to MES on some Linux Pilots.

Before your environment moves

Section titled “Before your environment moves”
  1. Inventory file-based integrations (EDI, BarTender, carrier software, imports and exports) and update their paths. This is the biggest source of breakage.
  2. Review custom code. Epicor provides a Linux compatibility report that flags problem code, but it has missed real problems, including function libraries with compile errors. Open and compile your function libraries and BPMs yourself in Pilot after it moves; don’t rely on the report alone.
  3. Shorten long SSRS report style names.
  4. Record the URLs your integrations use, and retest them after the move.
  5. Test in Pilot once it’s on Linux, with the same checklist you’d use for an upgrade, before Live is scheduled.
  6. Watch the known issues list Epicor staff maintain (linked in the sources below), and the EpiUsers threads, which often find problems first.

After the move

Section titled “After the move”

If something breaks, check Kinetic administration troubleshooting for the known symptoms. For file share access problems there’s no self-service fix beyond correcting your own paths: open a case.

Sources

This page is written in our own words. It was informed by: