# pvpython can not be used in kubernets
**URL:** https://discourse.paraview.org/t/pvpython-can-not-be-used-in-kubernets/13692
**Category:** Web Support
**Tags:** python
**Created:** [January 14, 2024, 12:20pm UTC](https://discourse.paraview.org/t/pvpython-can-not-be-used-in-kubernets/13692 "2024-01-14T12:20:32Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Lv\_Xuxin](https://discourse.paraview.org/u/Lv_Xuxin)
#### Post date: [January 14, 2024, 12:20pm UTC](https://discourse.paraview.org/t/pvpython-can-not-be-used-in-kubernets/13692/1 "2024-01-14T12:20:33Z")
I want to create a web visualization application based on ParaView. I used code from the trame framework. When building the Docker image, I adopted the Linux version downloaded from the official website: ParaView-5.12.0-RC1-osmesa-MPI-Linux-Python3.10-x86\_64.
Part of my Dockerfile is as follows:
dockerfileCopy code
```auto
FROM python:3.10
## Install ParaView
ARG paraview=ParaView-5.12.0-RC1-osmesa-MPI-Linux-Python3.10-x86_64
COPY ${paraview}.tar.gz /tmp/
RUN tar -xzf /tmp/${paraview}.tar.gz -C /tmp/ && \
mv /tmp/${paraview} /opt/paraview && \
rm -rf /tmp/${paraview}.tar.gz
RUN apt-get update && \
apt-get install -y libgl1-mesa-glx libgl1-mesa-dri
ENV PATH="/opt/paraview/bin:${PATH}"
```
I was able to launch pvpython on my own computer using `docker run -idt MyImage pvpython`. However, when I deploy it to the Kubernetes server, it throws an error:
cssCopy code
````auto
root@paraview-7f688cf59f-c2h46:/app# pvpython
error: exception occurred: Illegal instruction
```"
````
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [January 16, 2024, 9:25pm UTC](https://discourse.paraview.org/t/pvpython-can-not-be-used-in-kubernets/13692/2 "2024-01-16T21:25:38Z")
Is the K8s server running an older CPU at all?
---
### Author:  [@Lv\_Xuxin](https://discourse.paraview.org/u/Lv_Xuxin)
#### Post date: [January 18, 2024, 10:56am UTC](https://discourse.paraview.org/t/pvpython-can-not-be-used-in-kubernets/13692/3 "2024-01-18T10:56:11Z")
My server’s cpu is Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
here is some information that i use lscpu in terminal:
Architecture: x86\_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 40 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 16
On-line CPU(s) list: 0-15
Vendor ID: GenuineIntel
Model name: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
CPU family: 6
Model: 44
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 2
Stepping: 2
Frequency boost: enabled
CPU(s) scaling MHz: 68%
CPU max MHz: 2400.0000
CPU min MHz: 1600.0000
BogoMIPS: 4800.12
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx pdpe1gb rdtscp lm constant\_tsc arch\_perfmon pebs bts rep\_good nopl xtopology nonstop\_tsc cpuid aperfmperf pni dtes64 monitor ds\_cp
l vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4\_1 sse4\_2 popcnt lahf\_lm epb pti ssbd ibrs ibpb stibp tpr\_shadow vnmi flexpriority ept vpid dtherm ida arat flush\_l1d
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 256 KiB (8 instances)
L1i: 256 KiB (8 instances)
L2: 2 MiB (8 instances)
L3: 24 MiB (2 instances)
NUMA:
NUMA node(s): 2
NUMA node0 CPU(s): 0-3,8-11
NUMA node1 CPU(s): 4-7,12-15
Vulnerabilities:
Gather data sampling: Not affected
Itlb multihit: KVM: Mitigation: Split huge pages
L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable
Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Meltdown: Mitigation; PTI
Mmio stale data: Unknown: No mitigations
Retbleed: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Spectre v1: Mitigation; usercopy/swapgs barriers and \_\_user pointer sanitization
Spectre v2: Mitigation; Retpolines, IBPB conditional, IBRS\_FW, STIBP conditional, RSB filling, PBRSB-eIBRS Not affected
Srbds: Not affected
Tsx async abort: Not affected
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [January 19, 2024, 8:32pm UTC](https://discourse.paraview.org/t/pvpython-can-not-be-used-in-kubernets/13692/4 "2024-01-19T20:32:01Z")
> [@Lv\_Xuxin](#):
>
> My server’s cpu is Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
This seems to be a CPU from 2010 or so. I would call it too old for ParaView these days. We definitely have code that wants more advanced vectorization support than can be provided here.
Cc: @wascott @cory.quammen
---
### Author:  [@Lv\_Xuxin](https://discourse.paraview.org/u/Lv_Xuxin)
#### Post date: [January 20, 2024, 2:01am UTC](https://discourse.paraview.org/t/pvpython-can-not-be-used-in-kubernets/13692/5 "2024-01-20T02:01:28Z")
> [@ben.boeckel](#):
>
> This seems to be a CPU from 2010 or so. I would call it too old for ParaView these days. We definitely have code that wants more advanced vectorization support than can be provided here.
It seems that the CPU doesn’t support libOSmesa.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [January 20, 2024, 10:06pm UTC](https://discourse.paraview.org/t/pvpython-can-not-be-used-in-kubernets/13692/6 "2024-01-20T22:06:49Z")
Yes, I can imagine that OSMesa has a lot of vectorized code in it.