Skip to content

Commit

Permalink
Update doc for secure image using custom nginx config (#703)
Browse files Browse the repository at this point in the history
* Update doc for secure image using custom nginx config

* update per comment
  • Loading branch information
qiwzhang authored Sep 25, 2019
1 parent d57ae82 commit 5461d96
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ Normally ESP container runs as root, it is deemed as not secure. To make ESP con

You can switch to use the **secure images** if the followings are satisfied:
* Nginx is not listening on ports requiring root privilege (ports < 1024).
* Not use custom nginx config. The server_config path is hard coded to /etc/nginx/ folder in the custom nginx config. The secure image moved the server_config to /home/nginx. Please modify your custom nginx config before using the secure image.
* If a custom nginx config is used and it has the *server_config* path set to "/etc/nginx", the secure image will not work. The *server_config* is moved to the "/home/nginx" folder in the secure image. Please replace "/etc/nginx" with "/home/nginx" for *sever_config" in your custom nginx config before using the secure image.

If some folders can be mounted externally, the root system can be made read-only. Please see this GKE deployment [yaml](/test/bookstore/gke/deploy_secure_template.yaml) file as example on how to make root system read-only.

Expand Down

0 comments on commit 5461d96

Please sign in to comment.