DEV Community

loading...

Discussion on: Demystifying Docker Compose

Collapse
yujinyuz profile image
Yujin

I hope this doesn't sound stupid but why didn't we just do

COPY . /my-api
RUN bundle install

instead of the longer version

COPY Gemfile /my-api/Gemfile
COPY Gemfile.lock /my-api/Gemfile.lock
Copying the Gemfiles to the working space in the container.

RUN bundle install
This will run bundler in the container.

COPY . /my-api
Copy all the other files into the working space.

Is there a huge difference between the two?

Great article btw!

Collapse
geekgalgroks profile image
Jenn Author

Each line is cached, so if I only use COPY . /my-api I will have to run bundler every time anything in my code changes, which takes time and would be annoying.

By copying over the gemfiles first and running bundler those packages are cached and rebuilds will be faster. As docker-compose is smart enough to realize those files didn't change so it will skip the gemfile and bundler steps when building.

Collapse
yujinyuz profile image
Yujin

Ahh. That makes sense. Thanks for clearing things up for me 😁

Collapse
killrazor profile image
Tyler Christian

You could instead use a volume in docker-compose

Thread Thread
geekgalgroks profile image
Jenn Author

It wouldn't change the need to rebuild and rerun bundler if the gemfiles changed. I always prefer to rebuild the container when updating gemfiles. I don't want my docker-compose file to get out of sync with what happens in my container.