# Backwards compatibility for rancher-compose?

**URL:** <https://forums.suse.com/t/backwards-compatibility-for-rancher-compose/3003>\
**Category:** Rancher 1.x\
**Created:** [June 2, 2016, 3:38pm UTC](https://forums.suse.com/t/backwards-compatibility-for-rancher-compose/3003 "2016-06-02T15:38:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![andyshinn](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/andyshinn/32/442_2.png) [@andyshinn](https://forums.suse.com/u/andyshinn)\
**Post date:** [June 2, 2016, 3:38pm UTC](https://forums.suse.com/t/backwards-compatibility-for-rancher-compose/3003/1 "2016-06-02T15:38:00Z")

</div>

I’m wondering if rancher-compose 0.8.2 should work OK with Rancher 1.0.1? I’m trying to get the multiple docker-compose.yml file support in it. But running into an issue where environment variables being passed through become `nil`.

Is this possibly a bug or do I need to upgrade to 1.1.x?

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [June 4, 2016, 5:37am UTC](https://forums.suse.com/t/backwards-compatibility-for-rancher-compose/3003/2 "2016-06-04T05:37:21Z")

</div>

@andyshinn The `nil` environment variable issue is also occurring on v1.1.0-dev3. There was a big change between v0.7.4 -\> v0.8.0 where rancher-compose synced with the most recent libcompose changes, so not sure what happened.

Relevant github issue:

> <https://github.com/rancher/rancher/issues/4990>

---

<div class="post-metadata">

**Author:** ![andyshinn](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/andyshinn/32/442_2.png) [@andyshinn](https://forums.suse.com/u/andyshinn)\
**Post date:** [June 4, 2016, 5:13pm UTC](https://forums.suse.com/t/backwards-compatibility-for-rancher-compose/3003/3 "2016-06-04T17:13:54Z")

</div>

Ah, I searched but didn’t find that issue. Looks like the same thing I’m getting. I’ll subscribe. Thanks!