Local volumes (from host) via conversion

[johnament]

I'm trying to get my feet wet with Kubernetes. Since we already had a lot of investment in docker-compose I figured I'd try kompose to convert my docker-compose.yml into kubernetes service definitions.

When I do the conversion, I get this warning:

WARN Volume mount on the host "/Users/spartan/src/my-app/docker/custom-scripts" isn't supported - ignoring path on the host

My volume looks like this in docker-compose

    volumes:
      - "../docker/custom-scripts:/custom"

Is there another format I should use?

[surajnarwade]

we don't support volume mount on host with kompose, you can use emptyDir though

[johnament]

That's fine, I don't mind editing the files after the conversion. Wouldn't I want a hostPath though? Can hostPath be relative?

[cdrage]

Hey John! Due to how Kubernetes handles volumes, it's difficult to pass in a host volume / root volume. We are adding support for hostPath however, as one of our outside contributors is pushing it via PR: #734

[johnament]

@cdrage understood. It's more of a case where I think I can edit the volume definition afterwards.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[cdrage]

/remove-lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[ghost]

/reopen

[k8s-ci-robot]

@tuyenpm9: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[PeterBocan]

/remove-lifecycle rotten

[cuongnd-zigexn]

/reopen

[k8s-ci-robot]

@cuongnd-zigexn: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pirate]

@surajnarwade bump, it looks like this got auto-closed.

[hangyan]

/reopen

[k8s-ci-robot]

@hangyan: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[pirate]

/remove-lifecycle rotten

[hangyan]

close by #1216 . Now convert/up support --volumes=configMap to mount the files via configmap