Terminate the project

[julien-duponchelle]

Hi @bfirsh with docker 1.3 out should we replace the whole project by a link to boo2tdocker?

[lukaswelte]

:+1: Was a really cool project, but with the introduction of volume sharing to boot2docker I think there is no point to further maintain docker-osx as boot2docker is officially supported and moving a lot faster right now.

[andrewcstewart]

Does boot2docker have the fancy host namespace (ie, 'localdocker')? imho, that's always been the most important feature of docker-osx.

[mmerickel]

It is not named localdocker, you still need to do that yourself. However yes all of the ports are available on a dedicated IP just like docker-osx. They've done a good job of copying the best parts of docker-osx at this point.

[andrewcstewart]

imho, until it automatically creates its own boot2docker namespace or similar, I’ll continue happily using docker-osx.  I don’t personally see boot2docker as a better alternative at this point.

— Sent from Mailbox

On Sun, Oct 19, 2014 at 5:42 PM, Michael Merickel notifications@github.com wrote:

It is not named localdocker, you still need to do that yourself. However yes all of the ports are available on a dedicated IP just like docker-osx. They've done a good job of copying the best parts of docker-osx at this point.

Reply to this email directly or view it on GitHub: https://github.com/noplay/docker-osx/issues/75#issuecomment-59672778

[mmerickel]

It hosts everything at 192.168.52.103, so all you have to do is adjust the line in your /etc/hosts file. Dropping the dependency on vagrant is nice and it has good support for updating to new ISOs when new versions of docker are released. Anyway, I'll just say I've been using docker-osx longer than my friends but boot2docker is finally to the point where I felt it was smoother to setup than docker-osx.

[bfirsh]

I'd say not replace the whole project, for the sake of people still using it for Actual Work. But we should definitely say it's deprecated and (presumably) not maintained.

Thanks for your work on docker-osx btw – it was very much the inspiration for getting a /Users mount in boot2docker itself!

[lukaswelte]

And I started to experience some problems with the Volume sharing in boot2docker. Just root can write files somehow…

[bfirsh]

@lukaswelte Could you open an issue on the boot2docker project describing your issue in detail? https://github.com/boot2docker/boot2docker

Thanks!

[lukaswelte]

@bfirsh There is already a issue there and linked to the 1.3.1 milestone. But this is off topic in here ;)

[julien-duponchelle]

I just add a bug scary warning. I hope we can drop the project soon :)

[andrewcstewart]

Any chance of encouraging boot2docker to adopt the rest of the docker-osx feature set before doing so?

— Sent from Mailbox

On Tue, Oct 21, 2014 at 8:38 AM, Julien Duponchelle notifications@github.com wrote:

I just add a bug scary warning. I hope we can drop the project soon :)

Reply to this email directly or view it on GitHub: https://github.com/noplay/docker-osx/issues/75#issuecomment-59947910

[bfirsh]

@andrewcstewart The only thing missing now is a hostname, and we're working on that: https://github.com/boot2docker/boot2docker/pull/497

[j0hnsmith]

boot2docker doesn't support utf8 filenames, this prevents me from mounting samba shares with utf8 filenames into containers. This is the main reason why I use docker-osx.

I just installed the latest version of boot2docker (1.4.1) and

G_FILENAME_ENCODING=iso8859-1
LANG=C

are still there. I can't imagine that this is hard to fix @bfirsh, see https://github.com/boot2docker/boot2docker/issues/277