You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Honestly I don't know if this is at all actionable but just wanted to provide some feedback on an issue I had. Perhaps could add a note to README?
I used the old fig version of this fine and then recently pulled master to use docker-compose now it has changed name.
I'm on OS X with boot2docker but I had docker 1.2.0 still.
Building the kafka image here failed due to inability to fetch from apache mirrors with cryptic return value (8). But I noticed that the env vars were wonky inside the docker container. This is result of logging directly into the intermediate container that was used in the failed build step:
I'm not sure if support for multiple ENV assignments on one line was a recent addition (docs don't say when it was introduced) or if something else was going on but upgrading to docker 1.5.0 seems to have fixed whatever the issue was...
If you care about supporting older docker, you could go back to ENV FOO BAR syntax which apparently works but I'm not really sure it's worth your time - you might like to add a note to README though.
The text was updated successfully, but these errors were encountered:
Hi,
Honestly I don't know if this is at all actionable but just wanted to provide some feedback on an issue I had. Perhaps could add a note to README?
I used the old fig version of this fine and then recently pulled master to use docker-compose now it has changed name.
I'm on OS X with boot2docker but I had docker 1.2.0 still.
Building the kafka image here failed due to inability to fetch from apache mirrors with cryptic return value (8). But I noticed that the env vars were wonky inside the docker container. This is result of logging directly into the intermediate container that was used in the failed build step:
I'm not sure if support for multiple ENV assignments on one line was a recent addition (docs don't say when it was introduced) or if something else was going on but upgrading to docker 1.5.0 seems to have fixed whatever the issue was...
If you care about supporting older docker, you could go back to
ENV FOO BAR
syntax which apparently works but I'm not really sure it's worth your time - you might like to add a note to README though.The text was updated successfully, but these errors were encountered: