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

Not able to start services that has data volumes from other containers. #1334

Closed
sangeethah opened this Issue Jun 25, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@sangeethah
Member

sangeethah commented Jun 25, 2015

Server version - v0.25.0-rc2
Rancher compose version - rancher-compose-v0.1.3

Create a service that has data volumes from a container with label con=vol.
Service has scheduling rules to start a containers on host that has containers with labels con=vol.

I get the following error when trying to start the service:

root@sangee01:/home/sangeethahariharan1/rancher-compose-v0.1.3# ./rancher-compose -p testvol create
INFO[0000] Creating environment testvol
ERRO[0000] Failed to find 736073f0-2bb3-47aa-aa7c-02a90abc806e
INFO[0000] Creating service test41261
ERRO[0000] Failed to start test41261 : Bad response from [http://104.154.37.50:8080/v1/services], statusCode [422]. Status [422 status code 422]. Body: [{"id":"58318398-d51d-4fe7-b1d1-e30a565697b3","type":"error","links":{},"actions":{},"status":422,"code":"InvalidReference","message":null,"detail":null,"fieldName":"LaunchConfigName"}]
ERRO[0000] Failed to start: test41261 : Bad response from [http://104.154.37.50:8080/v1/services], statusCode [422]. Status [422 status code 422]. Body: [{"id":"58318398-d51d-4fe7-b1d1-e30a565697b3","type":"error","links":{},"actions":{},"status":422,"code":"InvalidReference","message":null,"detail":null,"fieldName":"LaunchConfigName"}]
FATA[0000] Bad response from [http://104.154.37.50:8080/v1/services], statusCode [422]. Status [422 status code 422]. Body: [{"id":"58318398-d51d-4fe7-b1d1-e30a565697b3","type":"error","links":{},"actions":{},"status":422,"code":"InvalidReference","message":null,"detail":null,"fieldName":"LaunchConfigName"}]
root@sangee01:/home/sangeethahariharan1/rancher-compose-v0.1.3#

ymls used:

docker-compose.yml

test41261:
  restart: on-failure:10
  labels:
    io.rancher.scheduler.affinity:container_label: c1=vol
  dns:
  - 1.2.3.4
  cpu_shares: 400
  image: ibuildthecloud/helloworld:latest
  hostname: test
  volumes:
  - /test/container:/test/vol1:ro
  stdin_open: true
  mem_limit: 8000000
  cap_add:
  - CHOWN
  dns_search:
  - 1.2.3.4
  environment:
    TEST_FILE: /etc/testpath.conf
  domainname: rancher.io
  cap_drop:
  - KILL
  tty: true
  command:
  - sleep
  - '9000'
  privileged: true
  volumes_from:
  - 736073f0-2bb3-47aa-aa7c-02a90abc806e
  user: root

rancher-compose.yml

test41261:
  scale: 2

@sangeethah sangeethah added this to the Release 1.0 milestone Jun 25, 2015

@sangeethah sangeethah changed the title from Not able to start services that have links to containers. to Not able to start services that has data volumes from other containers. Jun 26, 2015

@deniseschannon

This comment has been minimized.

Member

deniseschannon commented Jul 17, 2015

With Rancher-compose v0.2.1, this should work. You will need to make sure to use the sidekick label.

@sangeethah

This comment has been minimized.

Member

sangeethah commented Jul 21, 2015

This is the use case where the service needs data volumes from other container not data volumes from other services.
In this use case , volumes_from points to another container in the host (volumes_from: 736073f0-2bb3-47aa-aa7c-02a90abc806e) . Is this supported use case ?

@ibuildthecloud

This comment has been minimized.

Member

ibuildthecloud commented Sep 9, 2015

This is not a supported use case at the moment.

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