docker-compose build fails with error

[mister-monster]

Service 'web' failed to build: The command 'bash -c cd /opt/mastodon && bundle config set deployment 'true' && bundle config set without 'development test' && bundle install -j$(nproc) && yarn install --pure-lockfile' returned a non-zero code: 16

modified the Dockerfile to break apart these commands, the command causing problems is

The command 'bash -c bundle install -j$(nproc)

with this error

Don't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.
Could not locate Gemfile

I believe this is to do with installing the gem bundle? Not that familiar with ruby.

fails on release 1.0.5 (latest stable release as of this comment) and on Ubuntu server 20.04, if that helps.

Edit: changed this comment due to errors in my initial write up.

[mister-monster]

I believe I have narrowed it down to this error:

Could not find sidekiq-unique-jobs-6.0.18 in any of the sources

which is the first error I receive upon fresh cloning the repo and attempting docker-compose build.

possibly due to this mhenrixon/sidekiq-unique-jobs#471 (comment)

[MaybeThisIsRu]

There's also an automated PR to bump this dependency for security reasons anyway (I guess?). Note that this is a major version bump!

[MaybeThisIsRu]

If you cloned the repo like me, make sure you're actually check out the v1.0.5 tag: git checkout v1.0.5+3.2.0 before bringing up the containers. I just got around to setting mine up and this did the trick. There's probably work on the master branch for the v3.3.0 Mastodon release causing a mismatch between the Gemfile and the lock file: 8462b3e.

[leopku]

@hirusi Thanks for your remind.

Coping Gemfile.lock from original mastodon repo can make docker building passed.

I'm testing others.

[MaybeThisIsRu]

Coping Gemfile.lock from original mastodon repo can make docker building passed.

@leopku It's better if you download the source code ZIP from here and use that: https://github.com/hometown-fork/hometown/releases/tag/v1.0.5%2B3.2.0. Direct link: https://github.com/hometown-fork/hometown/archive/v1.0.5+3.2.0.zip

[leopku]

@hirusi Thank you.

I'm just wanna test hometown as 3.3.0 version.

I'll also test 3.2.0 later.

[leopku]

After days of reinstalling and reinstalling, I finished testing of Hometown.
Now my instance stayed in 1.0.5+3.2.0.

I will be glad to upgrade to 1.0.6+3.3.0 A.S.A.P after Hometown official released.

[decentral1se]

Thank you @leopku and @hirusi! #650 (comment) worked for me also.

I git cloned the mastodon repo and checkout out the same tag there as the one I want to build here in Hometown. I copied over the lock file also.

[dariusk]

@mister-monster Did this ever get resolved? I would investigate but we are talking about fairly old Hometown versions now.