New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fig Compatibility #2

Closed
thedug opened this Issue Jan 30, 2015 · 12 comments

Comments

Projects
None yet
5 participants
@thedug

thedug commented Jan 30, 2015

Have you ever used fig volumes with your vagrant image?

I've been using boot2docker and performance is terrible, so I've been working on setting up Vagrant/NFS rather than relying on the VBoxFS.

I tried another Vagrant/Boot2Docker fork but the volumes don't mount.

Thought I would ping you in case you've already tried it.

@seeruk

This comment has been minimized.

Show comment
Hide comment
@seeruk

seeruk Feb 7, 2015

Owner

I've not actually tried it, no. I do understand that handling volumes (and the filesystem in general) is tricky with Docker on OS X.

I'm actually only using Docker in production now, rather than in development, as it seems to work much easier that way.

Sorry this is a week later, I've been very busy with work!

Owner

seeruk commented Feb 7, 2015

I've not actually tried it, no. I do understand that handling volumes (and the filesystem in general) is tricky with Docker on OS X.

I'm actually only using Docker in production now, rather than in development, as it seems to work much easier that way.

Sorry this is a week later, I've been very busy with work!

@vsolovyov

This comment has been minimized.

Show comment
Hide comment
@vsolovyov

vsolovyov Feb 11, 2015

We're using this with fig and it actually works.

The only problem we're running into is the problem with devicemapper like this:

Service 'migrations' failed to build: Error getting container 904bfffe74024ca9a29d5f077b6d44230ab8e8a4990f7ccd254055d8d2fe8b0d from driver devicemapper: Error mounting '/dev/mapper/docker-8:1-263156-904bfffe74024ca9a29d5f077b6d44230ab8e8a4990f7ccd254055d8d2fe8b0d' on '/var/lib/docker/devicemapper/mnt/904bfffe74024ca9a29d5f077b6d44230ab8e8a4990f7ccd254055d8d2fe8b0d': no such file or directory

When I'm building an image from Dockerfile it actually occurs at every other step. It doesn't happen with boot2docker, because boot2docker uses AUFS. So it would be very useful if this project used AUFS too, as it gets a little boring and slow to restart build for every other step.

We're using this with fig and it actually works.

The only problem we're running into is the problem with devicemapper like this:

Service 'migrations' failed to build: Error getting container 904bfffe74024ca9a29d5f077b6d44230ab8e8a4990f7ccd254055d8d2fe8b0d from driver devicemapper: Error mounting '/dev/mapper/docker-8:1-263156-904bfffe74024ca9a29d5f077b6d44230ab8e8a4990f7ccd254055d8d2fe8b0d' on '/var/lib/docker/devicemapper/mnt/904bfffe74024ca9a29d5f077b6d44230ab8e8a4990f7ccd254055d8d2fe8b0d': no such file or directory

When I'm building an image from Dockerfile it actually occurs at every other step. It doesn't happen with boot2docker, because boot2docker uses AUFS. So it would be very useful if this project used AUFS too, as it gets a little boring and slow to restart build for every other step.

@seeruk

This comment has been minimized.

Show comment
Hide comment
@seeruk

seeruk Feb 11, 2015

Owner

I'll see if I get some time to look into using AUFS. Is there a publicly available Docker image / Fig configuration that you know does this that I can use to test this issue with?

Owner

seeruk commented Feb 11, 2015

I'll see if I get some time to look into using AUFS. Is there a publicly available Docker image / Fig configuration that you know does this that I can use to test this issue with?

@vsolovyov

This comment has been minimized.

Show comment
Hide comment
@vsolovyov

vsolovyov Feb 11, 2015

Not that I know of, but if I'll find something or make it myself, I will certainly notify you

Not that I know of, but if I'll find something or make it myself, I will certainly notify you

@gmorse81

This comment has been minimized.

Show comment
Hide comment
@gmorse81

gmorse81 Feb 14, 2015

I am having this same issue. It seems that when a dockerfile uses the COPY command, then RUNs a command against the file that was just copied, docker does not see the newly created container (since it chains container builds together when it builds). Not sure this is specific to fig, but it also happening for me when running fig up to build and orchestrate a set of containers.

I am having this same issue. It seems that when a dockerfile uses the COPY command, then RUNs a command against the file that was just copied, docker does not see the newly created container (since it chains container builds together when it builds). Not sure this is specific to fig, but it also happening for me when running fig up to build and orchestrate a set of containers.

@seeruk

This comment has been minimized.

Show comment
Hide comment
@seeruk

seeruk Mar 3, 2015

Owner

Hi folks. I've just pushed a couple of small changes, and am hoping that the issue is resolved. I have since tried a fig setup using this on my MacBook Pro, and it all worked fine - I just let it do it's thing and it got the whole way through without a hiccup.

Please update your copy from this repo and give it another shot and see if you still encounter any issues please.

Also - I made it a little easier to configure the CPU count and memory of the machine, just specify the values you want in environment variables OCH_CPUS and OCH_MEMORY.

Owner

seeruk commented Mar 3, 2015

Hi folks. I've just pushed a couple of small changes, and am hoping that the issue is resolved. I have since tried a fig setup using this on my MacBook Pro, and it all worked fine - I just let it do it's thing and it got the whole way through without a hiccup.

Please update your copy from this repo and give it another shot and see if you still encounter any issues please.

Also - I made it a little easier to configure the CPU count and memory of the machine, just specify the values you want in environment variables OCH_CPUS and OCH_MEMORY.

@mewm

This comment has been minimized.

Show comment
Hide comment
@mewm

mewm Mar 4, 2015

Contributor

Now when docker-compose has replaced fig, I'm not experiencing the devicemapper issue anymore.

Contributor

mewm commented Mar 4, 2015

Now when docker-compose has replaced fig, I'm not experiencing the devicemapper issue anymore.

@seeruk

This comment has been minimized.

Show comment
Hide comment
@seeruk

seeruk Mar 5, 2015

Owner

Great stuff! :) I'll have to actually give compose a try tonight. I'm going to close this for now though.

Owner

seeruk commented Mar 5, 2015

Great stuff! :) I'll have to actually give compose a try tonight. I'm going to close this for now though.

@seeruk seeruk closed this Mar 5, 2015

@mewm

This comment has been minimized.

Show comment
Hide comment
@mewm

mewm Mar 5, 2015

Contributor

@seeruk Because I miss-configured disqus on my blog, your comments has been removed on my bog :/. The change needed from fig to docker-compose is just to rename the fig.yml to docker-compose.yml and then use the docker-compose runtime. (Check top change: mewm/ghost-mariadb-docker@8e50023 )

Contributor

mewm commented Mar 5, 2015

@seeruk Because I miss-configured disqus on my blog, your comments has been removed on my bog :/. The change needed from fig to docker-compose is just to rename the fig.yml to docker-compose.yml and then use the docker-compose runtime. (Check top change: mewm/ghost-mariadb-docker@8e50023 )

@seeruk

This comment has been minimized.

Show comment
Hide comment
@seeruk

seeruk Mar 5, 2015

Owner

No worries, thanks for letting me know. I'm glad it's that straightforward! :)

Owner

seeruk commented Mar 5, 2015

No worries, thanks for letting me know. I'm glad it's that straightforward! :)

@seeruk

This comment has been minimized.

Show comment
Hide comment
@seeruk

seeruk Mar 5, 2015

Owner

Just tried it out, worked flawlessly with docker-compose. Awesome :)

Owner

seeruk commented Mar 5, 2015

Just tried it out, worked flawlessly with docker-compose. Awesome :)

@mewm

This comment has been minimized.

Show comment
Hide comment
@mewm

mewm Mar 5, 2015

Contributor

Sweet! All safe and sound then 👍

Contributor

mewm commented Mar 5, 2015

Sweet! All safe and sound then 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment