Skip to content

Commit f902ae5

Browse files
committed
chore(workflow): add exec/logs docs
1 parent 23fcf2c commit f902ae5

2 files changed

Lines changed: 33 additions & 1 deletion

File tree

src/applications/managing-app-lifecycle.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ from every [Container][] making it easy to troubleshoot problems with your appli
105105

106106
Use `drycc logs` to view the log output from your deployed application.
107107

108-
$ drycc logs | tail
108+
$ drycc logs -f
109109
Dec 3 00:30:31 ip-10-250-15-201 peachy-waxworks[web.5]: INFO:oejsh.ContextHandler:started o.e.j.s.ServletContextHandler{/,null}
110110
Dec 3 00:30:31 ip-10-250-15-201 peachy-waxworks[web.8]: INFO:oejs.Server:jetty-7.6.0.v20120127
111111
Dec 3 00:30:31 ip-10-250-15-201 peachy-waxworks[web.5]: INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:10005

src/applications/managing-app-processes.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -214,6 +214,38 @@ echoed-lollipop-web-67cfc78bdc-fdx4n up (v2)
214214
echoed-lollipop-web-67cfc78bdc-h2vxf up (v2)
215215
```
216216

217+
## Get a Shell to a Running Container
218+
219+
Verify that the container is running:
220+
221+
```
222+
# drycc ps
223+
=== python-getting-started Processes
224+
--- web:
225+
python-getting-started-web-69b7d4bfdc-kl4xf up (v2)
226+
```
227+
228+
Get a shell to the running container:
229+
230+
```
231+
# drycc ps:exec python-getting-started-web-69b7d4bfdc-kl4xf -it -- bash
232+
```
233+
234+
In your shell, list the root directory:
235+
236+
```
237+
# Run this inside the container
238+
ls /
239+
```
240+
241+
Running individual commands in a container
242+
243+
```
244+
# drycc ps:exec python-getting-started-web-69b7d4bfdc-kl4xf -- date
245+
```
246+
247+
Use "drycc ps --help" for a list of global command-line (applies to all commands).
248+
217249
## Autoscale
218250

219251
Autoscale allows adding a minimum and maximum number of pods on a per process type basis. This is accomplished by specifying a target CPU usage across all available pods.

0 commit comments

Comments
 (0)