I’m trying this on Ubuntu 22.04 Rust’s cargo install seems to keep creating permission problems between what I have to install, compile and what gets published in the cargo “registry”, which causes issues at runtime when I run as lemmy:lemmy through systemctl.
If I run: cargo install lemmy_server --target-dir /usr/bin/ --locked --features embed-pictrs as a non-root user, I get permission denied issues with /usr/bin/.future-incompat-report.json and /usr/bin/release
If I run the build as a root user, and then manually copy the binaries to /usr/bin and chmod them to lemmy:lemmy, then try to run as lemmy:lemmy, it appears the binary is trying to access some “registry” files in /root/.cargo/registry (for which of course it does not have permissions.)
How do I fix this?
Here’s how I do it. Might be worth giving it a shot. This is on FreeBSD, but I doubt that matters.
git clone https://github.com/LemmyNet/lemmy.git lemmy
cd lemmy
git checkout 0.17.3
git submodule init
git submodule update --recursive --remote
echo "pub const VERSION: &str = \"$(git describe --tag)\";" > "crates/utils/src/version.rs"
cargo build --release
strip target/release/lemmy_server
Then copy target/release/lemmy_server to wherever you want to run it.
Thanks. On cargo build --release I get this
...
Compiling strum_macros v0.24.3
Compiling deadpool v0.9.5
Compiling tokio-postgres v0.7.8
Compiling enum_delegate v0.2.0
Compiling doku v0.20.0
Compiling jsonwebtoken v8.3.0
error: failed to run custom build command for `lemmy_utils v0.17.3 (/home/ubuntu/git-clones/lemmy/crates/utils)`
Caused by:
process didn't exit successfully: `/home/ubuntu/git-clones/lemmy/target/release/build/lemmy_utils-6fa456450f9c975a/build-script-build` (exit status: 1)
--- stdout
cargo:rerun-if-changed=translations/email/en.json
cargo:rerun-if-changed=translations/email/ko.json
cargo:rerun-if-changed=translations/email/pt.json
--- stderr
Error: Parse(InvalidParameters { key: "new_application_subject", missing: ["hostname"], unknown: ["instance"] })
warning: build failed, waiting for other jobs to finish...
ubuntu@xxx:~/git-clones/lemmy$
I’ve seen guys here making PR’s to docs and install scripts, hope someone gonna do the same after finding solution for your question.
Thanks.
So if I go on a mad chmod spree, making /usr/bin/lemmy_server and all of its dependencies readable/executable (which is super insecure) I finally get to this log message in journalctl:
Jun 07 13:50:57 ip-172-31-4-153 lemmy_server[3868]: thread 'main' panicked at 'C
ouldn't run DB Migrations', /home/ubuntu/.cargo/registry/src/index.crates.io-6f1
7d22bba15001f/lemmy_db_schema-0.17.3/src/utils.rs:165:25
Which is this code:
pub fn run_migrations(db_url: &str) {
// Needs to be a sync connection
let mut conn =
PgConnection::establish(db_url).unwrap_or_else(|_| panic!("Error connecting to {db_url}"));
info!("Running Database migrations (This may take a long time)...");
let _ = &mut conn
.run_pending_migrations(MIGRATIONS)
.unwrap_or_else(|_| panic!("Couldn't run DB Migrations"));
info!("Database migrations complete.");
}
Hope that helps someone figure this out.
I’m pretty unhappy that I can’t get this to work.
So I am able to build from the git repo.
Had to remove rust from apt (v 1.65)
And install rust from rustup (v 1.70)
That fixes the build, but now I still get this db migrations error on startup.
Jun 09 15:47:37 ip-x systemd[1]: Started Lemmy - A link aggregator for the fediverse.
Jun 09 15:47:37 ip-x lemmy_server[15239]: 2023-06-09T15:47:37.238544Z INFO lemmy_db_schema::utils: Running Database migrations (This may take a long time)...
Jun 09 15:47:37 ip-x lemmy_server[15239]: thread 'main' panicked at 'Couldn't run DB Migrations', crates/db_schema/src/utils.rs:165:25
Jun 09 15:47:37 ip-x lemmy_server[15239]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Jun 09 15:47:37 ip-x systemd[1]: lemmy.service: Main process exited, code=exited, status=101/n/a
I know it can connect to the db because I see it created some tables already.
I wonder if this is related to this warning regarding schema, which I see during the build.
warning: /root/git-clones/lemmy/crates/api_common/Cargo.toml: `default-features` is ignored for lemmy_db_schema, since `default-features` was not specified for `workspace.dependencies.lemmy_db_schema`, this could become a hard error in the future
