Fig caching mounted volumes #836
Comments
|
Can you reproduce the bug using just |
|
@aanand I'm facing similar issue but only with See example(look for BetterErrors config which i have removed locally): > tail config/environments/development.rb
# Adds additional error checking when serving assets at runtime.
# Checks for improperly declared sprockets dependencies.
# Raises helpful error messages.
config.assets.raise_runtime_errors = true
# Raises error for missing translations
# config.action_view.raise_on_missing_translations = true
config.cache_store = :memory_store
end
> fig up app
Attaching to app_1
app_1 | # Raises error for missing translations
app_1 | # config.action_view.raise_on_missing_translations = true
app_1 |
app_1 | config.cache_store = :memory_store
app_1 |
app_1 | # Allow any ip as we are running it in docker container
=== THIS SHOULD NOT BE HERE app_1 | BetterErrors::Middleware.allow_ip! =======
app_1 | end
> fig run app
# Adds additional error checking when serving assets at runtime.
# Checks for improperly declared sprockets dependencies.
# Raises helpful error messages.
config.assets.raise_runtime_errors = true
# Raises error for missing translations
# config.action_view.raise_on_missing_translations = true
config.cache_store = :memory_store
end
> docker run -v /vagrant:/myapp <CONTAINER_ID> tail config/environments/development.rb
# Adds additional error checking when serving assets at runtime.
# Checks for improperly declared sprockets dependencies.
# Raises helpful error messages.
config.assets.raise_runtime_errors = true
# Raises error for missing translations
# config.action_view.raise_on_missing_translations = true
config.cache_store = :memory_store
endFig.yml: /vagrant is folder synced to local folder using vagrant syncing. I don't think it has anything to do with vagrant as |
|
My problem is with fig up as well, I believe. |
|
Confirming the same problem with |
|
Have you tried with docker 1.5.0? |
|
@cpuguy83 yes docker-compose is with docker 1.5.0. |
|
@Maxim-Filimonov Are there any notable differences if you |
|
Confirming this issue using fig 1.0.1 and docker 1.4.1. The workaround is |
|
I confirmed that this is an issue still. The workaround to "rm then up" it worked, but it's less than idea. |
|
I'm also experiencing an issue similar to this. When I remove There's a key in that |
|
This would be fixed by #858 |
|
Upgrade to |
|
#858 has been merged into 1.3.0. This should be fixed once that is released. |
|
I experienced this twice today, on 2 different computers. rm & up helped |
|
Also experiencing this issue with |
|
I am still experiencing this issue with docker-compose 1.7.0. Has anybody found a workaround? |
|
@nathanjosiah Can you provide more details? Does it happen with the Docker CLI as well or just with Compose? What's the output of |
|
I've just observed the same behaviour. The host machine is a macbook running OSX. I'm running the virtualbox-based host (not the xhyve one). The output of docker inspect is as follows: The (local) edits I do to /Users/jguillaumes/git/simhdocker/test/pdpbsd/pdp11.ini are not "seen" by the container when I start it. The only way I've got to "refresh" it is:
Now, when I restart the container I see the updated file Version info: |
|
@aanand If I remember correctly, I ended up restarting the docker-machine and it was fine. |
After updating fig, I'm having a problem where fig seems to be caching the local working directory and using it's own version instead of using my local directory. For instance in my fig.yml I have
But file changes don't show in the web server.
In another project, where a volume is mounted the same way, switching branches in my local directory does not seem to update the code in the mounted volume.
Is this a new configuration item I am missing or something?
The text was updated successfully, but these errors were encountered: