PVE REST endpoints (/pve/*) return 404 in single-node Docker deployment

[xuang7]

What happened?

In the single-node Docker deployment, every time a Python UDF operator is selected in the workflow editor, an error popup appears:
Could not load Python virtual environments: ...

Selecting a Python operator triggers a GET /pve/pves?cuid= request (to populate the environment dropdown). In single-node Docker this request returns 404 Not Found.

How to reproduce?

1. Run the single-node Docker latest stack from main (bin/single-node).
2. Log in and open the workflow editor.
3. Drag a Python UDF operator onto the canvas and click it to open its property panel.
4. Observe the popup: "Could not load Python virtual environments: ..."

Version/Branch

1.2.0-incubating (release/v1.2)

Commit Hash (Optional)

No response

What browsers are you seeing the problem on?

No response

Relevant log output

[SarahAsad23]

/take

[Yicong-Huang]

does this happen on main as well? or only on release/v1.2?

[SarahAsad23]

This also occurs on main. The feature has changed quite a bit, and I haven't yet raised the PR that adds the corresponding Kubernetes configuration.

[kz930]

I reproduced this on the RC2 Docker images and traced the root cause.

Root cause: nginx.conf in the docker-compose bundle is out of sync with frontend/proxy.config.json. The frontend calls /pve/*, but the backend serves it under /api/pve/* on the runtime
coordinator. proxy.config.json rewrites ^/pve → /api/pve and forwards to :8085; nginx.conf has no /pve location, so the request falls through to the catch-all → dashboard-service → 404. That's
why it works in the dev setup but breaks in Docker.

Not isolated: the same gap breaks the computing-unit "Share access" feature. The frontend calls /api/access/computing-unit/{list,owner,grant,revoke}/<id> (endpoint exists on
computing-unit-managing:8888, returns 401 when hit directly), but nginx.conf has no route for it, so it also 404s via the catch-all.

Suggested fix — add to nginx.conf before the location / fallback:

location /pve/ {                                                                                                                                                                                               
    rewrite ^/pve/(.*)$ /api/pve/$1 break;                                                                                                                                                                     
    proxy_pass http://workflow-runtime-coordinator-service:8085;                                                                                                                                               
    proxy_set_header Host $host;                                                                                                                                                                               
    proxy_set_header X-Real-IP $remote_addr;                                                                                                                                                                   
}                                                                                                                                                                                                              
                                                                                                                                                                                                               
location /api/access/computing-unit/ {                                                                                                                                                                         
    proxy_pass http://workflow-computing-unit-managing-service:8888;                                                                                                                                           
    proxy_set_header Host $host;                                                                                                                                                                               
    proxy_set_header X-Real-IP $remote_addr;                                                                                                                                                                   
}                                                                                                                                                                                                              

Verified on the RC2 stack: /pve/pves went 404 → 200, and /api/access/computing-unit/owner/1 went 404 → reaches the service. Worth auditing nginx.conf against proxy.config.json for any other missing
routes before the next RC.

[Yicong-Huang]

Thanks, @xuang7, @SarahAsad23 and @kz930. Let's fix this in main and backport to v1.2 (separate fix if they have diverged).