You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to test run Grav make changes to it and wanted to retain the changes.
The container process for grav is not staying in memory. Its exiting.
This test was on a windows 7 Enterprise (SP1) desktop with the below
$ docker version
Client:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Tue Apr 26 23:44:17 2016
OS/Arch: windows/amd64
Server:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 21:20:08 2016
OS/Arch: linux/amd64
$ docker run -i --rm garywiz/docker-grav --task get-launcher | sh
$ mkdir docker-grav-storage
$./run-docker-grav.sh -d
The text was updated successfully, but these errors were encountered:
[root@localhost grav]# mkdir docker-grav-storage
[root@localhost grav]# ./run-docker-grav.sh -d
Using attached storage at /home/grav/docker-grav-storage
864b8773e763d73b05ba3050080fc67de6652e22e8d76d3be1e0332723559061
[root@localhost grav]# cd docker-grav-storage/
[root@localhost docker-grav-storage]# ls
[root@localhost docker-grav-storage]# cd ..
[root@localhost grav]# ls
docker-grav-storage run run-docker-grav.sh
[root@localhost grav]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
864b8773e763 garywiz/docker-grav "/usr/local/bin/chape" 17 seconds ago Exited (1) 14 seconds ago angry_williams
[root@localhost grav]# docker logs 86
There are no services configured to run, nor is there a command specified
on the command line to run as an application. You need to do one or the other.
[root@localhost grav]#
@dberuben your problem is different. Note that this container will not run as root. It's designed so that all processes inside the container run as a more secure user. So, if you try the same thing from a non-root user, things should be fine. I have a new version of the container nearing release.... but it will still disallow running as root. It will just provide better error diagnostics. Admittedly, the above is confusing!
I wanted to test run Grav make changes to it and wanted to retain the changes.
The container process for grav is not staying in memory. Its exiting.
This test was on a windows 7 Enterprise (SP1) desktop with the below
$ docker version
Client:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Tue Apr 26 23:44:17 2016
OS/Arch: windows/amd64
Server:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 21:20:08 2016
OS/Arch: linux/amd64
$ docker run -i --rm garywiz/docker-grav --task get-launcher | sh
$ mkdir docker-grav-storage
$./run-docker-grav.sh -d
The text was updated successfully, but these errors were encountered: