missing gems after docker_dev_update

Jump to solution
hmoffatt
Community Member

I have Canvas from 2022-02 for development running in Docker and I'd like to update it to the latest.

I've fetched the latest from git and I'm running docker_dev_update.sh, which fails with

docker-compose.override.yml exists, skipping copy of default configuration


> Bringing Canvas up to date ...
  Log file is /home/hamish/src/canvas-lms/log/docker_dev_update.log

> There have been some updates made to Dockerfile, you should rebuild your docker images.
Rebuild docker images? [y/n] y

> Rebuilding docker images...  [DONE]

> Starting docker containers...[DONE]

> Checking your gems (bundle check)... [DONE]

>   Installing gems (bundle install) ...       [FAIL]

  /o\ Something went wrong. Check /home/hamish/src/canvas-lms/log/docker_dev_update.log for details.

 

The log ends with

 

Checking your gems (bundle check)...
Following files may not be writable, so sudo is needed:
  /home/docker/.gem
  /home/docker/.gem/bin
  /home/docker/.gem/bin
  /home/docker/.gem/build_info
  /home/docker/.gem/build_info/ffi-1.13.1.info
  /home/docker/.gem/build_info/nokogiri-1.12.5-x86_64-linux.info
  /home/docker/.gem/bundler
  /home/docker/.gem/cache
  /home/docker/.gem/doc
  /home/docker/.gem/extensions
  /home/docker/.gem/gems
  /home/docker/.gem/plugins
  /home/docker/.gem/ruby
  /home/docker/.gem/specifications
The git source https://github.com/rails-api/active_model_serializers.git is not
yet checked out. Please run `bundle install` before trying to start your
application
  Installing gems (bundle install) ...
  /o\ Something went wrong. Check /home/hamish/src/canvas-lms/log/docker_dev_update.log for details.

 

I'm not sure what to do here as I think all the bundling is meant to happen inside the containers, ie I shouldn't have to install anything extra on the host. /home/docker does not exist on the host.

How can I fix this?

Thanks

0 Likes
1 Solution
hmoffatt
Community Member

There were all sorts of permission errors with the old checkout. Once I fixed those up, I found that the Postgres container had been updated from 12 to 14 with no way to migrate its data, so it wouldn't start.

So I gave up and installed it from scratch.

View solution in original post

0 Likes