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?

  • RoundSparrow@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Front end:

    Are your ‘git pull’ instructions incomplete? I did:
    git clone https://github.com/LemmyNet/lemmy-ui.git --recursive .

    • Grouchy@lemmy.grouchysysadmin.com
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago

      Yes, my instructions above are only for Lemmy. Here’s my complete setup.

      1: Build Lemmy
      cd /root
      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
      
      2: Build lemmy-ui
      cd /root
      git clone https://github.com/LemmyNet/lemmy-ui.git --recursive lemmy-ui
      cd lemmy-ui
      git checkout 0.17.3
      yarn install --pure-lockfile
      yarn build:prod
      
      3: Built pict-rs
      cd /root
      git clone https://git.asonix.dog/asonix/pict-rs.git pictrs
      cd pictrs
      git checkout v0.3.3
      cargo build --release
      strip target/release/pict-rs
      

      I’m running the binaries generated from those instructions at my own instance. Again, this is FreeBSD, not Linux, so your results may vary. I can’t imagine there’s any real difference though. I suspect the errors you’re getting are due to missing dependencies on your OS.