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.

Sign up for GitHub

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

Jump to bottom

Workaround calcio not declaring DirectoryOrCreate on hostPath volumes #113

Merged
merged 1 commit into from Apr 28, 2024
Merged

Workaround calcio not declaring DirectoryOrCreate on hostPath volumes #113

merged 1 commit into from Apr 28, 2024

Conversation

consideRatio
Copy link
Member

@consideRatio consideRatio commented Apr 28, 2024 •
edited

We observe #112, specifically that calico-node pod fails to startup because:

    Warning  Failed     7m35s (x12 over 9m44s)  kubelet            Error: Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /opt/cni/bin

Which relates to a calcio manifest having this, but doesn't have type: DirectoryOrCreate under hostPath alongside path.

        # Used to install CNI.
        - name: cni-bin-dir
          hostPath:
            path: /opt/cni/bin

Fixes #112

@consideRatio consideRatio mentioned this pull request Apr 28, 2024
Merged
@consideRatio consideRatio changed the title Update calico from 3.27.0 to 3.27.3 Workaround regression in latest k3s when --docker is enabled Apr 28, 2024
@consideRatio consideRatio force-pushed the pr/update-calico branch 2 times, most recently from e51dd56 to bb9f91f Compare April 28, 2024 15:44
@consideRatio consideRatio mentioned this pull request Apr 28, 2024
Closed
@consideRatio consideRatio changed the title Workaround regression in latest k3s when --docker is enabled Workaround regression in latest k3s when --docker is enabled - calcio fails to install Apr 28, 2024
@consideRatio consideRatio changed the title Workaround regression in latest k3s when --docker is enabled - calcio fails to install Workaround recently introduced failure to startup calico-node in latest k3s with --docker Apr 28, 2024
@consideRatio consideRatio force-pushed the pr/update-calico branch 3 times, most recently from a3adb47 to f969596 Compare April 28, 2024 16:00
@consideRatio consideRatio changed the title Workaround recently introduced failure to startup calico-node in latest k3s with --docker Workaround calcio not declaring DirectoryOrCreate on hostPath volumes Apr 28, 2024
@consideRatio consideRatio added the bug Something isn't working label Apr 28, 2024
@consideRatio consideRatio merged commit d0311b2 into jupyterhub:main Apr 28, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Calico not compatible with latest k3s 1.29 version
1 participant
@consideRatio