flatheadmill / homeport Goto Github PK

when I run either
./homeport create --user joshua --hub jgpelletier
or
./homeport create --user joshua --account jgpelletier
I get ./homeport: line 111: /getopt.bash: No such file or directory

When docker/env/create is run after ./homeport configure --user joshua --hub jgpelletier the console logs docker/env/create: line 5: /Users/joshua/.homeport: No such file or directory. Is this expected?

I built homeport and got it to launch, yay. Now I'm looking at how to get some more packages installed, especially a few that I end up compiling or loading every time I get to a new system. What did you have in mind to handle that?

Create a listing of available tagged images.

Share home directories using Samba or NFS. Provide a URL that will simplify mounting in the host using mount or Finder.

Instead of building form source, Homeport should build from a Docker image.

Specify a formula using a relative path. Formula are saved on the image to be reused at flatten time.

Or maybe in general, so that the build process is not so chatty.

Launching SSH linked to other containers you loose the environment settings when you SSH in. Attempt to save the environment and set it for new connections.

http://serverfault.com/a/388831

Ask me anything.

• List available tagged images.

After updating to master, I receive this error when trying to run:

FATA[0000] Error response from daemon: Could not apply volumes of 
non-existent container "homeport_home_joshua_joshua".  
error in run: exit status 1

I run homeport run and it does launch the expected Ubuntu shell, but then it complains about .ssh-agent. Does that sound familiar?

Edwards-MacBook-Air:homeport emv$ ./homeport run
chown: cannot access '/home/emv/.ssh-agent': No such file or directory

Create a launch script that will change to the desired user.

Start up might be faster if you SSH into the server, instead of running it directly.

So one way to get applications onto a Mac through brew is to set up a tap with your own repo with its own install instructions. That might be useful for homeport.

https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/brew-tap.md

is the docs.

I downloaded via git and put homeport in my source tree, and then tried to run it and got this:

Edwards-MacBook-Air:homeport emv$ ./homeport 
Unable to find image 'bigeasy/env:latest' locally
Pulling repository bigeasy/env
FATA[0002] Error: image bigeasy/env:latest not found    
error in run: exit status 1

I don't know if I missed a step prior to doing this.

Create a program that will establish the environment common to most commands, then launch the command, like git this or docker that.

Here's a new install method:

$ docker run --rm homeport/homeport install --arg=value | bash

That would create a bash script that would build a homeport. This homeport would create your home directories and create a bootstrapped shell. You might want to use zsh so you'd do something like

$ docker run --rm homeport/homeport append zsh formula/chsh:alan,/usr/bin/zsh | bash

This way you can implement formula/gem csv.

Make the whole system work on a Raspberry Pi. At minimum this means a separate build that targets ARM systems.

Instead of a generated image because they you cannot regenerate the image.

there's lots of errors sprinkled throughout the install from debconf being unable to pose questions under docker.
debconf: unable to initialize frontend: Dialog debconf: (TERM is not set, so the dialog frontend is not usable.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (This frontend requires a controlling tty.) debconf: falling back to frontend: Teletype dpkg-preconfigure: unable to re-open stdin:

see here. http://stackoverflow.com/questions/22466255/is-it-possibe-to-answer-dialog-questions-when-installing-under-docker

I shouldn't have to cd to the Homeport project directory for common formulas.

I receive this message after homeport run.

here
docker\ run\ --rm\ -it\ -u\ josh\ -v\ \$\(readlink\ -f\ \$SSH_AUTH_SOCK\):/ssh-agent\ -e\ SSH_AUTH_SOCK=/ssh-agent\ -h\ homeport\ --volumes-from\ homeport_home_alan\ homeport_shell:joshua\ /home/josh/.homeportrcFATA[0000] Error response from daemon: Could not apply volumes of non-existent container "homeport_home_alan". 
error in run: exit status 1

I realize this is something endemic to Docker, but it's worth noting to see if there's a simple solution to it.

If you do a series of homeport append commands, intermediate images are left behind that are big.

REPOSITORY                 TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
homeport_emv_emv_default   latest              0a24d3b2dd95        About an hour ago   498.5 MB
<none>                     <none>              f4caa06aced3        About an hour ago   494.7 MB
<none>                     <none>              fa253b313d32        About an hour ago   494.7 MB
<none>                     <none>              d226063eac56        2 hours ago         320.7 MB
<none>                     <none>              75f4ae62e84c        2 hours ago         320.7 MB
homeport_emv_emv_default   foundation          2d67d1028efe        2 hours ago         240.5 MB
ubuntu                     latest              6d4946999d4f        2 weeks ago         188.3 MB

It would be useful to have (or to document) a way to purge the old unneeded images.