Invidious: Outdated shard.lock (pg requirements changed). Please run shards update instead.

[tleydxdy]

when running docker-compose build

[omarroth]

Should be fixed with 62f7f7a689ea08a8d680d221780d20def319b271.

Also added instructions for updating with Docker to the wiki, which should fix a potential issue with an outdated Crystal version.

[tleydxdy]

new error

Error in src/invidious.cr:1141: undefined method 'verify' for Crypto::Bcrypt::Password
      if Crypto::Bcrypt::Password.new(user.password.not_nil!).verify(password.byte_slice(0, 55))

[omarroth]

That's the issue I was referring to above with an outdated version. You'll want to make sure your base images are up-to-date using the instructions in the wiki.

[tleydxdy]

yep, this error comes up when using those commands

[atahanacar]

I get this error when trying to update using the instructions in the wiki.

Error in src/invidious.cr:1159: undefined method 'verify' for Crypto::Bcrypt::Password

      if Crypto::Bcrypt::Password.new(user.password.not_nil!).verify(password.byte_slice(0, 55))
                                                              ^~~~~~

Rerun with --error-trace to show a complete error trace.
ERROR: Service 'invidious' failed to build: The command '/bin/sh -c sed -i 's/host: localhost/host: postgres/' config/config.yml &&     shards update && shards install &&     crystal build src/invidious.cr' returned a non-zero code: 1

[atahanacar]

Found a workaround. First, I had to start a bash shell inside the docker container.
docker exec -it invidious_invidious_1 bash
Then, I updated the required packages
pacman -Sy shards crystal imagemagick librsvg which pkgconf gcc ttf-liberation glibc
Stashed the changes (because of my custom config), pulled and unstashed them.
git stash && git pull && git stash pop
Finally, built the updated version.
crystal build src/invidious.cr
After all these steps, restarted the docker container and everything was forking fine. I guess the main problem was with the git part. I am a noob when it comes to docker so I have no clue.

[leonklingele]

This should be fixed now that #665 is merged.

[atahanacar]

I've used the method I've previously mentioned to update to the latest commit. I'll test it once the a commit arrives.

[atahanacar]

Update: It works as expected now.

[omarroth]

I'd like to confirm the issue is fixed for @tleydxdy as well before closing this.

[tleydxdy]

yep it works! and glad that build doesn't take nearly as much ram now.