Ruby version is 2.7.1, but your Gemfile specified 2.7.2 #48

New Issue

2021-01-25T19:03:16Z

kawaiipunk commented

2021-01-25 19:03:16 +00:00

Just chucking this here:

docker-compose up
Starting autonomiczone_jekyll_1 ... done
Attaching to autonomiczone_jekyll_1
jekyll_1  | Your Ruby version is 2.7.1, but your Gemfile specified 2.7.2
autonomiczone_jekyll_1 exited with code 18

Does this mean the upstream image's ruby version is out of date?

Just chucking this here: ``` docker-compose up Starting autonomiczone_jekyll_1 ... done Attaching to autonomiczone_jekyll_1 jekyll_1 | Your Ruby version is 2.7.1, but your Gemfile specified 2.7.2 autonomiczone_jekyll_1 exited with code 18 ``` Does this mean the upstream image's ruby version is out of date?

kawaiipunk added the bug label 2021-01-25 19:03:38 +00:00

kawaiipunk commented

2021-01-25 19:15:43 +00:00

Workaround is just changing Gemfile to specify 2.7.1

kawaiipunk commented

2021-01-25 19:19:18 +00:00

Guessing our comrade bot did this:
961cf1a54d

Guessing our comrade bot did this: https://git.autonomic.zone/autonomic-cooperative/autonomic.zone/commit/961cf1a54dee1248b70c4ef6df126315be48deb1

decentral1se referenced this issue from a commit

2021-01-26 11:22:28 +00:00

Use the same image all over the place

decentral1se closed this issue

2021-01-26 11:22:28 +00:00

decentral1se commented

2021-01-26 11:23:15 +00:00

Thanks for raising and investigating! Looks like yes, the bot is upgrading configs and then I setup the dev vs. prod to use different images which got us out of sync on the ruby versions. Sooo, I switched the dev setup to use the same image now and we shouldn't run into this again, I hope.

This repo is archived. You cannot comment on issues.

2 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: autonomic-cooperative/autonomic.zone#48