Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
After consultation with the DO support team I think that what is causing the problem is that first the Docker image is deployed and then the persistent volume is claimed and the fs is mounted with an empt dir and therefore, replacing the current files.
I put this option in the YAML file for the deployment case:
lifecycle:
postStart:
exec:
command: ["/bin/sh", "-c", "touch /var/www/html/index.html"]
After this addition, I am not getting a 403 error, but the empty index.html page that is created.
So now the question is how can I prevent the pv claim from deleting my docker image files.
Basically the log file messages are of the following categories:
Though the www folder size is much much less than 1GB, I also tried with 5GB capacity. I still have the same issues.
Hello,
This actually looks correct. Have you tried checking your pod logs?
kubectl logs -f pod_name -c container_name
Also, I can see that you are setting your PVC storage to 1GB, is it possible that your /var/www/html folder is larger than that? Have you tried setting the size to 5GB, for example, depending of course on the size of the actual folder inside your container?
Regards, Bobby