Upgrade Rails to 7.1, update dependencies, require Ruby 3.x #160
Labels
No Label
integration
discourse
integration
ejabberd
integration
ldap
integration
lndhub
integration
nostr
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Depends on
#167 Allow admins to add and remove invitations per account
kosmos/akkounts
#168 Fix Ruby in Docker container on Apple silicon
kosmos/akkounts
Reference: kosmos/akkounts#160
Loading…
Reference in New Issue
No description provided.
Delete Branch "chore/update_dependencies"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It only started with me wanting to publish Manifique on rubygems.org, which created a bit of a hole-in-a-bucket situation that ended with updating all dependencies and upgrading everything for Ruby 3 (only).
nostr
gem, because we don't need our Ruby 2.7 compat branch anymoremanifique
gemHint for reviews: files changed look way worse than what it is. Most files are just switching to keyword arguments for service calls. Going commit by commit should be pretty quick and easy.
WIP: Upgrade Rails to 7.1, update dependencies, require Ruby 3.xto Upgrade Rails to 7.1, update dependencies, require Ruby 3.xChanges look all good to me.
Still can't run the docker containers on my Mac, so wasn't able to test it myself yet.
The error looks like you created a new Redis container at some point, and it's unable to overwrite data from an older one. Whenever you see permission issues with anything in
tmp/
, just delete the directory and try again.Since that error caused the stopping of the other containers, the second error just means the container isn't running, as it says.
I cleared the whole tmp directory beforehand. Didn't work.
So it started with an empty tmp directory and the listing in the screenshot shows what's been created by the
docker compose up
I have no idea why it wouldn't be able to run
chown
on a directory it created itself.That's actually similar to what I suspect is the issue on @greg's (Intel-based) Mac (albeit with the LDAP container there). Maybe @slvrbckt has an idea for how to proceed? Unfortunately, I do not have a Mac, so I am unable to debug macOS-related Docker issues. :/
Hey guys, tell me what command to try and I will try it out, I have an M1 mac. I am just busy with work so unfortunately I don't have time to investigate on my own atm.
I'm currently trying a fresh checkout, on the
chore/update_dependencies
branch, the commanddocker compose up
End of
docker compose up
output:@slvrbckt that looks like you have another LDAP running already.
Correct, I do. However turning it off doesn't change the result. Also, redis doesn't bind to port 389, at least not by default.
Oh, forgot to check
docker ps
which shows a third service,akkounts-liquor-cabinet
, running.I think this is from before @galfert changed his reply to say LDAP instead of Redis?
389 is the default port for plaintext LDAP connections (hence the name 389ds of the LDAP server implementation we're using). So you'd need to check what's running on that port on your host system in order to prevent the conflict. Alternatively, you could comment the port forwarding for the
ldap
service/container indocker-compose.yml
.Ah OK, well I don't have LDAP running that I know of, but no matter, I commented out the port forwarding just to make sure things build. That seems to work:
Although it looks like there were two of those services that exited right away:
web
andsidekiq
Ruby backtrace for
web
container:Ruby backtrace for
sidekiq
container:Upgrade Rails to 7.1, update dependencies, require Ruby 3.xto WIP: Upgrade Rails to 7.1, update dependencies, require Ruby 3.x@galfert @slvrbckt Turns out Ruby 3.3.0 is broken on Apple silicon. Could you try the fix in #168, please?
If that one works, then we can merge it here and then also back to #162.
Good to go on them newfangled MacBooks now.
(Thanks for helping with that, @slvrbckt! 🙏)
Everything starts up now without any obvious errors. I can log in as admin, however when testing #168, after logging in as admin I was presented with a list of users. Now when I log in as admin I just have a blank content area. Not sure if this is unexpected or not.
EDIT: There are no errors in the docker logs when I log in.
Marking as approved, as everything starts up fine now... (unless that blank content area I mentioned is an actual issue).
There would not be a list of users on the root URL, but only on
/admin/users
. The dashboard would contain links for any enabled services, like Chat etc..There are no services enabled by default1. See
.env.example
for some examples, and use.env.development
for your local testing (which is ignored by Git).except for remoteStorage, but it's still hidden behind a feature flag, and in order for it to work fully with Docker Compose and minimal setup, there is #162 open to merge into here. You can go to http://localhost:3000/flipper and add "remotestorage" as a feature, then enable it for all users. (Requires https://gitea.kosmos.org/kosmos/akkounts#minio--rs) ↩︎
WIP: Upgrade Rails to 7.1, update dependencies, require Ruby 3.xto Upgrade Rails to 7.1, update dependencies, require Ruby 3.x