Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

My broken container is gone - how to debug containers on container platforms

306 visualizaciones

Publicado el

How to troubleshoot micro-services when services auto-recover, containers get deleted and there is nothing left to troubleshoot?

Talk given at SwissRE TecCon19 on March 14th 2019 in Zürich, Switzerland

Publicado en: Software
  • Sé el primero en comentar

My broken container is gone - how to debug containers on container platforms

  1. 1. My broken container is gone - where is my container ?
  2. 2. ● ● ● ○ ○ ○ ○ ○ ○ ○ ○ ○ Agenda
  3. 3. → → → About Aarno & VSHN.ch
  4. 4. ● ○ ○ ○ ○ ○ ● ○ ○ ○ ○ Container technology: Docker
  5. 5. ● ● ● ● ● Container orchestration: Kubernetes
  6. 6. Kubernetes Example apiVersion: apps/v1beta1 kind: Deployment metadata: name: hello-deploy spec: replicas: 2 template: metadata: labels: app: hello spec: containers: - name: hello image: arska/flask-helloworld:1 ports: - containerPort: 8080 env: - name: MESSAGE value: "This is my config value"
  7. 7. ● ● ● ● ● ● ● Kubernetes Distributions
  8. 8. ● ○ ○ ○ ○ ● ● ● Cloud native IT governance
  9. 9. ● ● ● ● ● ● Design your application for robustness
  10. 10. ● ● ● ● ● Running an application in a container
  11. 11. ● ○ ○ ● ○ ○ ○ ● ○ ● Local build/start debugging
  12. 12. ● ○ ○ ● ○ ○ ● ○ ○ ○ If your application doesn’t start
  13. 13. ● ○ ○ ● ○ ● ○ If your application starts but behaves strangely
  14. 14. ● ● ○ ○ ○ ○ ○ ○ bad data on persistent volume
  15. 15. ● ● Have you tried turning it off and on again?
  16. 16. ● ● ● Errors during build on the platform
  17. 17. ● ● ○ ● ○ ○ Errors during deployment
  18. 18. ● ● ● ● Volume mount fails
  19. 19. ● errors due to running as root in container $ oc new-app thesteve0/centoshttpd ... * WARNING: Image "thesteve0/centoshttpd" runs as the 'root' user which may not be permitted by your cluster administrator ... $ oc get pods NAME READY STATUS RESTARTS AGE centoshttpd-1-46gt6 0/1 CrashLoopBackOff 4 2m $ oc logs dc/centoshttpd AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 10.1.10.84. Set the 'ServerName' directive globally to suppress this message (13)Permission denied: AH00058: Error retrieving pid file /run/httpd/httpd.pid AH00059: Remove it before continuing if it is corrupted.
  20. 20. Come visit us for a coffee! https://vshn.ch/kontakt/

×