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

multiple containers in a pod sharing volume #1012

Closed
choig opened this Issue May 17, 2018 · 5 comments

Comments

Projects
None yet
4 participants
@choig

choig commented May 17, 2018

When I use kompose up or kompose convert, I get each service as its own pod with single container. One functionality I am trying to use in kubernetes is the docker-in-docker (dind) that sits along side my execution agent in the same pod. I have this working with kubectl create if using the same emptyDir to share both workspace and docker.sock for both containers. I also have this working with docker-compose but this does not convert over to kubernetes without multiple containers in a pod support.

I have gone thru the docs and do not see mention of multiple container pod. Plus in other forums, I have seen the same question posted without any solution. Thus I am posting here after seeing the RFE for service type. Along the same lines of kompose.service.type that can switch to loadbalancer, I wondered if it would be possible to:

  • use a specific label that can group services/containers together into a pod
  • and also iterate over the volume mounts that share the same location to be combined together when --volumes emptyDir is present
@fejta-bot

This comment has been minimized.

fejta-bot commented Aug 15, 2018

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

This comment has been minimized.

fejta-bot commented Sep 14, 2018

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

@korentsov

This comment has been minimized.

korentsov commented Sep 26, 2018

I've also faced with this issue, I need to use gcePersistentDisk as ReadWrite in multiple containers, which is possible only with multi-container pod.

I agree with choig, would be good to have:

  • use a specific label that can group services/containers together into a pod
  • and also iterate over the volume mounts that share the same location to be combined together when --volumes emptyDir is present
@fejta-bot

This comment has been minimized.

fejta-bot commented Oct 26, 2018

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

@k8s-ci-robot

This comment has been minimized.

k8s-ci-robot commented Oct 26, 2018

@fejta-bot: Closing this issue.

In response to this:

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

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment