"permission denied" error is seen in the deployment POD when using jammy stack.
search cancel

"permission denied" error is seen in the deployment POD when using jammy stack.

book

Article ID: 297899

calendar_today

Updated On:

Products

VMware Tanzu Application Service for VMs

Issue/Introduction

permission denied error message can be seen in the deployment Pod when using jammy stack.

$ kubectl -n <Namespace> logs <Deployment-Pod>
Defaulted container "workload" out of: workload, queue-proxy
...
<i> [webpack-dev-server] Content not from webpack is served from '/workspace/public' directory
<e> [webpack-dev-middleware] Error: EACCES: permission denied, unlink '/workspace/dist/app.bundle.js'
...


Environment

Product Version: 1.5

Resolution

  • This is a known issue and the root cause of the issue is the mismatch between build-time UID and run-time UID. (build-time UID=1001 and run-time UID=1000 in the affected TAP versions).
  • This known issue has been fixed in TAP (Tanzu Application Platform) 1.5.2 and both build-time & run-time UID will be 1000. So the solution is to upgrade the TAP foundation to 1.5.2 to solve the issue.