在ssh会话中访问Google引擎灵活的应用文件? [英] Access app files in ssh session into google app engine flexible?

问题描述

我正在设置一个基于PHP的Google App Engine灵活环境项目，如果我可以访问在/app中运行的PHP文件，那么对我来说(以进度速度而言)会容易得多.在 SSH 会话中，而Google Cloud Console可以在网络浏览器中正常显示.

I'm setting up a PHP based Google App Engine Flexible Environment project and it would be much easier going for me (in terms of speed of progress) if I could access the PHP files that are running at /app in the SSH session that the Google Cloud Console so gracefully provides right in the web browser.

不幸的是，我找不到与此相关的信息.我可以看到 mount 命令的输出，看起来好像已经安装了很多路径，但是没有一个线索可以找到我的/app :>在/sys类型sysfs上的

Unfortunately, there is no information that I can find pertaining to this. I can see the output of the mount command and it looks like a whole lot of paths are mounted, but none give a clue where my /app can be found:

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=191984,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=154052k,mode=755)
/dev/sda1 on / type ext4 (rw,relatime,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=308100k)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,mode=755)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_prio type cgroup (rw,relatime,net_prio)
/dev/sda1 on /var/lib/docker/aufs type ext4 (rw,relatime,data=ordered)
none on /var/lib/docker/aufs/mnt/a8141f5169b6d62d3baeb5d0da713cdf77a2a5524ba492a579a8af9963f2aba4 type aufs (rw,relatime,si=5f839818bd3efaaa,dio,dirperm1)
shm on /var/lib/docker/containers/11aafe10a4269e66ffef7b09dd07d0793e1793bf17a287311e9cdc26bca39a25/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
proc on /run/docker/netns/b3fa6a6ae075 type proc (rw,nosuid,nodev,noexec,relatime)
none on /var/lib/docker/aufs/mnt/5b5758049ca6d6c65eddcffcc1d18be01d5337a0ccd27b9f7a80d417495ccf95 type aufs (rw,relatime,si=5f839818a368baaa,dio,dirperm1)
shm on /var/lib/docker/containers/08ba8f0c4ba4a1373f5c6723f4ed2b76c88994a9b5ef3f47dc100b833f39233d/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
proc on /run/docker/netns/b94901bac194 type proc (rw,nosuid,nodev,noexec,relatime)
none on /var/lib/docker/aufs/mnt/6fee2ea01a6311aaf32767351e2635e03d20c2bcdff3034bdf8145e672f1ab3e type aufs (rw,relatime,si=5f839818a32d5aaa,dio,dirperm1)
shm on /var/lib/docker/containers/8d81f94a6c7381323b8f8fb86fbc4546db03bdbc68cc537a0684be32773f921e/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
proc on /run/docker/netns/db581b9dfbd7 type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /mnt/app_volumes/mnt/ramdisk1 type tmpfs (rw,relatime,size=104448k)
none on /var/lib/docker/aufs/mnt/cd6c2ddbddf1a871e9e5da6b7ebe2515da0002829aca2fb9eb598b48c3c4ad8f type aufs (rw,relatime,si=5f839818a0d6baaa,dio,dirperm1)
shm on /var/lib/docker/containers/a16282fee594fc5d38ef3185b8442f15f16d2f496f49a5748536067ac3826840/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
proc on /run/docker/netns/f14af5f2d130 type proc (rw,nosuid,nodev,noexec,relatime)
none on /var/lib/docker/aufs/mnt/bf58f8c8520fb2113364cbd31709159c36f09bceff53239cd42e238ed53fd357 type aufs (rw,relatime,si=5f839818b97b5aaa,dio,dirperm1)
shm on /var/lib/docker/containers/e778b3781b6a8f4ab53bb925a9cd196da258c6e95c74c22eed029b2b3e4c7955/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
proc on /run/docker/netns/19a91926e87f type proc (rw,nosuid,nodev,noexec,relatime)

似乎正在使用docker运行我的应用程序，但是我无法列出容器，这是我使用 $ docker ps返回的内容无法连接到Docker守护程序.docker守护程序是否在此主机上运行?

It looks like docker is in use to run my app, but I am unable to list containers, this is what I get back using $docker ps Cannot connect to the Docker daemon. Is the docker daemon running on this host?

建议，指针将不胜感激！

Suggestions, pointers would be much appreciated!

推荐答案

$ sudo docker exec -t -i gaeapp /bin/bash
# Now you're in the app container!
# apt-get update && apt-get -y install vim

如果您使用的是opcache，则可能需要重新启动php-fpm.您可以通过以下方式重新启动所有内容:

If you're using opcache, you may need to restart the php-fpm. You can restart everything by:

# kill -HUP 1

这篇关于在ssh会话中访问Google引擎灵活的应用文件?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！