Welcome to the Linux Foundation Forum!

Lab 7: nginx:1.15.1 deprecated

Posts: 207
in LFS258 Class Forum

Hello,
It seems the nginx version used in the lab in not available anymore

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Comments

  • Posts: 207

    Well, some containers are fine and other not:

    1. ...
    2. Events:
    3.   Type    Reason     Age   From               Message
    4.   ----    ------     ----  ----               -------
    5.   Normal  Scheduled  12m   default-scheduler  Successfully assigned default/ds-one-9dwh2 to k8scp
    6.   Normal  Pulling    12m   kubelet            Pulling image "nginx:1.15.1"
    7.   Normal  Pulled     11m   kubelet            Successfully pulled image "nginx:1.15.1" in 7.617759384s
    8.   Normal  Created    11m   kubelet            Created container nginx
    9.   Normal  Started    11m   kubelet            Started container nginx
    10.  
    11.  
    12. ...
    13. Events:
    14.   Type     Reason     Age                  From               Message
    15.   ----     ------     ----                 ----               -------
    16.   Normal   Scheduled  11m                  default-scheduler  Successfully assigned default/ds-one-5lf8k to lf-ha-wn
    17.   Warning  Failed     8m15s (x4 over 11m)  kubelet            Failed to pull image "nginx:1.15.1": rpc error: code = Unknown desc = reading manifest 1.15.1 in quay.io/nginx: StatusCode: 404, <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final/...
    18.   Warning  Failed     8m15s (x4 over 11m)  kubelet            Error: ErrImagePull
    19.   Warning  Failed     8m3s (x6 over 11m)   kubelet            Error: ImagePullBackOff
    20.   Normal   Pulling    6m46s (x5 over 11m)  kubelet            Pulling image "nginx:1.15.1"
    21.   Normal   BackOff    110s (x28 over 11m)  kubelet            Back-off pulling image "nginx:1.15.1"
  • Posts: 207

    The containers with an issue are on the worker node, same with a redis deployment. The Cri is crio, there must be something I missed during the install.
    Or maybe it's the pod Cidr, I've set 192.168/16 and it could be too big for Aws

  • Posts: 207

    In file /etc/kubernetes/manifests/kube-controller-manager.yaml, I tried to set the Cidr to 192.169.0/24, but the nodes remain in 192.168/16:

    1. $ kubectl get nodes -o jsonpath='{.items[*].spec.podCIDR}'
    2. 192.168.0.0/24 192.168.1.0/24
  • Posts: 207

    Something must have gone wrong during the install, it's working now

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Quick Links

Categories

Upcoming Training