Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manifest unknown when pulling fluent-bit Windows image and missing from rancher-windows-images.txt #32016

Closed
izaac opened this issue Apr 9, 2021 · 6 comments
Assignees
Labels
area/air-gapped area/logging area/windows kind/bug Issues that are defects reported by users or that we know have reached a real release kind/enhancement Issues that improve or augment existing functionality priority/0
Milestone

Comments

@izaac
Copy link
Contributor

izaac commented Apr 9, 2021

What kind of request is this:
bug

Steps to reproduce:

  • Go to and download https://github.com/rancher/rancher/releases/tag/v2.5.8-rc2
    • rancher-save-images.ps1
    • rancher-windows-images.txt
    • Windows 2019 / or 1809
  • Use the rancher-save-images.ps1 script to pull rancher-windows-images.txt
  • add rancher/fluent-bit:1.6.10 as it's missing there
  • Execute rancher-save-images.ps1 (docker login --registry might be required)

Result:

Pulling rancher/fluent-bit:1.6.10-windows-1809
Error response from daemon: manifest for rancher/fluent-bit:1.6.10-windows-1809 not found: manifest unknown: manifest unknown

This doesn't load to a private registry used for Windows Airgap.

Other details that may be helpful:

ImagePullBackOff: Back-off pulling image "rancher/fluent-bit:1.6.10" Is seen when deploying the logging v2 chart

Logging 3.9.400-rc02

Environment information

  • Rancher version: v2.5.8-rc2
  • Installation option: single / airgap
@izaac izaac added the kind/bug Issues that are defects reported by users or that we know have reached a real release label Apr 9, 2021
@izaac izaac added this to the v2.5.8 milestone Apr 9, 2021
@izaac
Copy link
Contributor Author

izaac commented Apr 9, 2021

#28721

@izaac
Copy link
Contributor Author

izaac commented Apr 21, 2021

Rancher version v2.5.8-rc7
I ran into this error when the logging windows pods are getting created:

CreateContainerError: Error response from daemon: failed to start service utility VM (createreadwrite): kernel 'C:\Program Files\Linux Containers\kernel' not found

docker inspect returns OS linux:

 "Architecture": "amd64",
        "Os": "linux",
        "Size": 85041664,
        "VirtualSize": 85041664,
        "GraphDriver": {

This is the rancher-windows-images.txt content:

rancher/configmap-reload:v0.3.0-rancher4
rancher/fluentd:v0.1.24
rancher/hyperkube:v1.17.17-rancher2
rancher/hyperkube:v1.18.18-rancher1
rancher/hyperkube:v1.19.10-rancher1
rancher/hyperkube:v1.20.6-rancher1
rancher/kubelet-pause:v0.1.6
rancher/rancher-agent:v2.5.8-rc7
rancher/rke-tools:v0.1.74
rancher/wmi_exporter-package:v0.0.7

Image used in the downstream cluster:

<private-registry-url>/rancher/fluent-bit:1.6.10

@izaac
Copy link
Contributor Author

izaac commented Apr 27, 2021

Rancher version: v2.5.8-rc10

This is working on latest rc10.

This is a full end-to-end images save/load and Logging v2 deployment on AG Windows cluster:

k get all -n cattle-logging-system
NAME                                                READY   STATUS      RESTARTS   AGE
pod/rancher-logging-7c969c896-hc7nb                 1/1     Running     0          4m3s
pod/rancher-logging-fluentbit-ndjqv                 1/1     Running     0          3m49s
pod/rancher-logging-fluentbit-pcgnr                 1/1     Running     0          3m49s
pod/rancher-logging-fluentbit-svdcg                 1/1     Running     0          3m49s
pod/rancher-logging-fluentd-0                       2/2     Running     0          3m49s
pod/rancher-logging-fluentd-configcheck-c3054702    0/1     Completed   0          3m57s
pod/rancher-logging-rke-aggregator-99s2r            1/1     Running     0          4m3s
pod/rancher-logging-rke-aggregator-cnmm2            1/1     Running     0          4m3s
pod/rancher-logging-rke-aggregator-mt26x            1/1     Running     0          4m3s
pod/rancher-logging-win-agent-fluentbit-dvzhg       1/1     Running     0          3m49s
pod/rancher-logging-win-agent-rke-fluentbit-bhdtk   1/1     Running     0          3m49s

NAME                                       TYPE        CLUSTER-IP    EXTERNAL-IP   PORT(S)               AGE
service/rancher-logging                    ClusterIP   None          <none>        8080/TCP              4m3s
service/rancher-logging-fluentd            ClusterIP   10.43.19.92   <none>        24240/TCP,24240/UDP   3m49s
service/rancher-logging-fluentd-headless   ClusterIP   None          <none>        24240/TCP,24240/UDP   3m49s

NAME                                                     DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR              AGE
daemonset.apps/rancher-logging-fluentbit                 3         3         3       3            3           kubernetes.io/os=linux     3m49s
daemonset.apps/rancher-logging-rke-aggregator            3         3         3       3            3           kubernetes.io/os=linux     4m3s
daemonset.apps/rancher-logging-win-agent-fluentbit       1         1         1       1            1           kubernetes.io/os=windows   3m49s
daemonset.apps/rancher-logging-win-agent-rke-fluentbit   1         1         1       1            1           kubernetes.io/os=windows   3m49s

NAME                              READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/rancher-logging   1/1     1            1           4m3s

NAME                                        DESIRED   CURRENT   READY   AGE
replicaset.apps/rancher-logging-7c969c896   1         1         1       4m3s

NAME                                       READY   AGE
statefulset.apps/rancher-logging-fluentd   1/1     3m50s

@izaac izaac closed this as completed Apr 27, 2021
@shpwrck shpwrck added the kind/enhancement Issues that improve or augment existing functionality label May 4, 2021
@zube zube bot removed the [zube]: Done label Jul 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/air-gapped area/logging area/windows kind/bug Issues that are defects reported by users or that we know have reached a real release kind/enhancement Issues that improve or augment existing functionality priority/0
Projects
None yet
Development

No branches or pull requests

7 participants