Please rebuild progrium/envy; still uses HOST_DATA, not HOST_ROOT

[elimisteve]

Since https://hub.docker.com/r/progrium/envy/ uses HOST_DATA rather than HOST_ROOT, the instructions in the README no longer work; when I do -e HOST_DATA=/mnt/envy to start a container, I get this error when shelling in:

$ ssh envy 
Timestamp: 2016-01-30 21:40:18.794089272 -0500 EST
Code: System error

Message: not a directory

Frames:

---
0: setupRootfs
Package: github.com/opencontainers/runc/libcontainer
File: rootfs_linux.go@40

---
1: Init
Package: github.com/opencontainers/runc/libcontainer.(*linuxStandardInit)
File: standard_init_linux.go@57

---
2: StartInitialization
Package: github.com/opencontainers/runc/libcontainer.(*LinuxFactory)
File: factory_linux.go@242

---
3: initializer
Package: github.com/docker/docker/daemon/execdriver/native
File: init.go@35

---
4: Init
Package: github.com/docker/docker/pkg/reexec
File: reexec.go@26

---
5: main
Package: main
File: docker.go@18

---
6: main
Package: runtime
File: proc.go@63

---
7: goexit
Package: runtime
File: asm_amd64.s@2232
FATA[0000] Error response from daemon: Cannot start container 2c4bae1da20a5c69beb01f85c0e9915338f9027122e595228e746f8e2d1e7452: [8] System error: not a directory 
Connection to xx.yy.zz.ww closed.

If I start the container with -e HOST_ROOT as specified in the README, I get this when I shell in:

$ ssh envy
/bin/enterenv: line 5: HOST_DATA: parameter null or not set
Connection to xx.yy.zz.ww closed.

[progrium]

Cool. I was just coming back to this project, so I'll update docs and such when I do.

[elimisteve]

Great, thanks.

[lcmen]

@progrium any update on this?

[progrium]

Haven't had the need to work on this. Is it too much to build it yourself?

On Thu, Aug 31, 2017 at 4:10 PM, Lucas Mendelowski <notifications@github.com

wrote:

@progrium https://github.com/progrium any update on this?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/progrium/envy/issues/49#issuecomment-326421665, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAChzCPIJm0r1VIONTmvhxoqzDC8P5lks5sdyFZgaJpZM4HP8rG .

-- Jeff Lindsay http://progrium.com

[elimisteve]

Sure I can, but updating the official one might be good :-) though perhaps not urgent.

[lcmen]

@progrium it's not too much. The image just does not build anymore - there is a problem with go build.

[progrium]

If you get it to build, I'll merge a PR. Just don't have the cycles for this one, but helps to know people are trying it.

[josegonzalez]

@progrium any chance you can grant me access to this repo and docker hub access? My nick on docker hub is savant :)

[progrium]

done!

[josegonzalez]

Can you also add me to the docker hub repo? I don't see it in my list of repos, and going here doesn't show it.

Thanks!

[progrium]

I added you, does it require an email link click?

On Tue, May 7, 2019 at 11:07 PM Jose Diaz-Gonzalez notifications@github.com wrote:

Can you also add me to the docker hub repo? I don't see it in my list of repos, and going here https://hub.docker.com/r/progrium/envy doesn't show it.

Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/progrium/envy/issues/49#issuecomment-490339579, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAAFBYMEGGVAH7NAR5BQ4LPUJGYRANCNFSM4BZ7ZLDA .

-- Jeff Lindsay http://progrium.com

[josegonzalez]

Seems there are no notifications when you get added to a repo.

I've pushed a build of latest to docker hub. Enjoy everyone!