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

Support Socket HostPath type with 'play kube' command #7112

Closed
inflatador opened this issue Jul 28, 2020 · 2 comments · Fixed by #7494
Closed

Support Socket HostPath type with 'play kube' command #7112

inflatador opened this issue Jul 28, 2020 · 2 comments · Fixed by #7494
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue

Comments

@inflatador
Copy link

/kind feature

Description

Support Socket HostPath type with 'play kube' command

Steps to reproduce the issue:

  1. podman play kube kube.yml

Describe the results you received:
2. message: Error: Directories are the only supported HostPath type (note that this error message is incorrect, HostPath type 'File' is also supported)

Describe the results you expected:

Support Socket HostPath type with 'play kube' command

Additional information you deem important (e.g. issue happens only occasionally):
Example kube.yml

spec:
  volumes:
    - name: awx_redis_conf
      hostPath:
        path: /opt/podman/etc/redis.conf
        type: File
        
    - name: aws_redis_socket
      hostPath:
        path: /opt/podman/run/redis/redis.sock
        type: Socket
        
    - name: awx_redis 
      image: redis
      command:
        - redis-server
        - "/redis/redis.conf"
      volumeMounts: 
          - name: awx_redis_conf
            mountPath: /redis/redis.conf
            readOnly: true
          - name: aws_redis_socket
            mountPath: /redis/redis.sock
            readOnly: false

Output of podman version:

podman --version
podman version 2.0.3

Output of podman info --debug:

INFO[0000] podman filtering at log level info
WARN[0000] Error initializing configured OCI runtime crun: no valid executable found for OCI runtime crun: invalid argument
WARN[0000] Error initializing configured OCI runtime kata: no valid executable found for OCI runtime kata: invalid argument
INFO[0000] Found CNI network podman (type=bridge) at /etc/cni/net.d/87-podman-bridge.conflist
WARN[0000] Default CNI network name podman is unchangeable
INFO[0000] Setting parallel job count to 25
Error: Directories are the only supported HostPath type

Package info (e.g. output of rpm -q podman or apt list podman):

rpm -q podman
podman-2.0.3-1.el8.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):
CentOS 8 VM using podman installed from copr repo

@openshift-ci-robot openshift-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 28, 2020
@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Aug 28, 2020

@ashley-cui @haircommander PTAL

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants