# Rancher-compose & api keys

**URL:** <https://forums.suse.com/t/rancher-compose-api-keys/10430>\
**Category:** SUSE Rancher Prime\
**Created:** [May 15, 2018, 2:00pm UTC](https://forums.suse.com/t/rancher-compose-api-keys/10430 "2018-05-15T14:00:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tinky](https://avatars.discourse-cdn.com/v4/letter/t/8797f3/32.png) [@Tinky](https://forums.suse.com/u/Tinky)\
**Post date:** [May 15, 2018, 2:00pm UTC](https://forums.suse.com/t/rancher-compose-api-keys/10430/1 "2018-05-15T14:00:14Z")

</div>

Hi Rancher community,

I try to get provision a project using rancher-compose. Using a user key results in the following error message:

Failed to open project XXX: Can not create a stack, check API key [token-pvfzd] for [https://rancher\_url/v3]? Failed to read project: Can not create a stack, check API key [token-pvfzd] for [https://rancher\_url/v3]

checking google, i saw you need to rather need to create an environment api key via API: https://rancher\_url/v3/apikeys  
However, this url does not exist…  
Resources -\> API Keys in the UI also seems to have vanished…

Any ideas?

---

<div class="post-metadata">

**Author:** ![cjellick](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/cjellick/32/2876_2.png) [@cjellick](https://forums.suse.com/u/cjellick)\
**Post date:** [May 15, 2018, 4:25pm UTC](https://forums.suse.com/t/rancher-compose-api-keys/10430/2 "2018-05-15T16:25:28Z")

</div>

`rancher-compose` does not work in in v2.0. You must do things the kubernetes way. The closest equivalent to rancher-compose in 2.0 is Helm or raw Kubernetes yaml files + `kubectl apply -f <file.yaml>`

---

<div class="post-metadata">

**Author:** ![Jan\_Poboril](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/jan_poboril/32/2778_2.png) [@Jan\_Poboril](https://forums.suse.com/u/Jan_Poboril)\
**Post date:** [August 4, 2018, 11:54pm UTC](https://forums.suse.com/t/rancher-compose-api-keys/10430/3 "2018-08-04T23:54:24Z")

</div>

Am I wrong you promised v2 will have support for docker-compose.yml, because it was one of the most loved feature of Cattle?

---

<div class="post-metadata">

**Author:** ![Conan](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/conan/32/3700_2.png) [@Conan](https://forums.suse.com/u/Conan)\
**Post date:** [August 5, 2018, 11:58pm UTC](https://forums.suse.com/t/rancher-compose-api-keys/10430/4 "2018-08-05T23:58:26Z")

</div>

There is undocumented Rancher CLI up command in v2.0.4-rc1.  
Rancher up is not document in [https://rancher.com/docs/rancher/v2.x/en/cli/](https://rancher.com/docs/rancher/v2.x/en/cli/)  
Is it intends to run old rancher-compose file? If not and only Helm and raw Kubernetes yaml files available in command line. How you going to work around this issue? [https://github.com/rancher/docs/issues/278](https://github.com/rancher/docs/issues/278)  
That discourage people to use Rancher UI

Rancher CLI, managing containers one UTF-8 character at a time  
Usage: rancher [OPTIONS] COMMAND [arg…]

Version: v2.0.4-rc1  
Options:  
–debug Debug logging  
–help, -h show help  
–version, -v print the version

Commands:  
apps, [app] Operations with apps  
catalog Operations with catalogs  
clusters, [cluster] Operations on clusters  
context Operations for the context  
inspect View details of resources  
kubectl Run kubectl commands  
login, [l] Login to a Rancher server  
namespaces, [namespace] Operations on namespaces  
nodes, [node] Operations on nodes  
projects, [project] Operations on projects  
ps Show workloads in a project  
settings, [setting] Show settings for the current server  
ssh SSH into a node  
**up apply compose config**  
help, [h] Shows a list of commands or help for one command