# Downstream cluster provisioning issues using docker instalation

**URL:** <https://forums.suse.com/t/downstream-cluster-provisioning-issues-using-docker-instalation/40379>\
**Category:** SUSE Rancher Prime\
**Created:** [March 29, 2023, 1:28pm UTC](https://forums.suse.com/t/downstream-cluster-provisioning-issues-using-docker-instalation/40379 "2023-03-29T13:28:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Herman\_Milton\_Maleia](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/herman_milton_maleia/32/9633_2.png) [@Herman\_Milton\_Maleia](https://forums.suse.com/u/Herman_Milton_Maleia)\
**Post date:** [March 29, 2023, 1:28pm UTC](https://forums.suse.com/t/downstream-cluster-provisioning-issues-using-docker-instalation/40379/1 "2023-03-29T13:28:43Z")

</div>

Hi Team,

I´m facing some issues when i try to perform provisioning of downstream cluster.  
Can you please help with this issue.

Failed to apply the ServiceAccount needed for job execution: Post “[https://10.2.28.126:6443/apis/rbac.authorization.k8s.io/v1/clusterrolebindings?timeout=30s](https://10.2.28.126:6443/apis/rbac.authorization.k8s.io/v1/clusterrolebindings?timeout=30s)”: Forbidden

From provisioning logs

[INFO] [authz] Creating rke-job-deployer ServiceAccount  
3:57:04 pm [ERROR] Failed to apply the ServiceAccount needed for job execution: Post “[https://10.2.28.126:6443/apis/rbac.authorization.k8s.io/v1/clusterrolebindings?timeout=30s](https://10.2.28.126:6443/apis/rbac.authorization.k8s.io/v1/clusterrolebindings?timeout=30s)”: Forbidden

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/c/c8675c7e83ad3b9b13051645a6a832d3459348db.png)

---

<div class="post-metadata">

**Author:** ![Herman\_Milton\_Maleia](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/herman_milton_maleia/32/9633_2.png) [@Herman\_Milton\_Maleia](https://forums.suse.com/u/Herman_Milton_Maleia)\
**Post date:** [March 30, 2023, 2:12pm UTC](https://forums.suse.com/t/downstream-cluster-provisioning-issues-using-docker-instalation/40379/2 "2023-03-30T14:12:06Z")

</div>

Solved.

If you are using rancher behind a corporate proxy just use no proxy for control plane in environment variables.

```auto
docker run -d --restart=unless-stopped \
  -p 80:80 -p 443:443 \
  -e HTTP_PROXY="" \
  -e HTTPS_PROXY="" \
  -e NO_PROXY="127.0.0.1,0.0.0.0,10.2.XXX.XXX,localhost,172.17.0.1,IP:6443" \
  --privileged \
  rancher/rancher:latest

```