# Viewing logs and launching shells NOT working

**URL:** <https://forums.suse.com/t/viewing-logs-and-launching-shells-not-working/8192>\
**Category:** Rancher 1.x\
**Created:** [January 10, 2018, 4:29pm UTC](https://forums.suse.com/t/viewing-logs-and-launching-shells-not-working/8192 "2018-01-10T16:29:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ranchboy](https://avatars.discourse-cdn.com/v4/letter/r/82dd89/32.png) [@ranchboy](https://forums.suse.com/u/ranchboy)\
**Post date:** [January 10, 2018, 4:29pm UTC](https://forums.suse.com/t/viewing-logs-and-launching-shells-not-working/8192/1 "2018-01-10T16:29:36Z")

</div>

When I create containers, I can use the gui to quickly launch (execute shell and view logs) However when I’ve created containers as part of a stack, those functions don’t work anymore. Is there something I’m missing here? Also I notice that the CPU/Memory stats gui just shows …“connecting…” Unlike the individual containers where I am able to see real stats. I have compare both configurations and I can’t really see and differences. Here’s a typical compose example

myapp:  
image: myrepo/app  
hostname: tum  
stdin\_open: true  
tty: true  
ports:  
- 9000:9000/tcp  
- 9010:9010/tcp  
labels:  
io.rancher.container.pull\_image: always

Do I have to add some options?
