Sqlx says that a Postgres URL is incorrect, but when I connect with psql it works perfectly.

[KOEGlike]

When I run docker compose up on my project, it says that postgresql://jammer:example_password@jam_db:5432/jam_db is incorrect, with the error: error with configuration: relative URL without a base. But when I terminal into the database container and run psql postgresql://jammer:example_password@jam_db:5432/jam_db it connects perfectly.

Here is the env file:

export SPOTIFY_ID="not_relevant"
export SPOTIFY_SECRET="not_relevant"
export POSTGRES_PASSWORD="example_password"
export DATABASE_URL="postgresql://localhost:5432/jam_db?user=jammer&password=${POSTGRES_PASSWORD}"

here is the compose file:

services:
  jam_db:
    container_name: jam_db
    image: postgres:latest
    shm_size: 500mb
    ports:
      - 5432:5432
    env_file:
      - .env
    environment:
      - POSTGRES_HOST_AUTH_METHOD=scram-sha-256
      - POSTGRES_INITDB_ARGS=--auth-host=scram-sha-256
      - POSTGRES_USER=jammer
      - POSTGRES_DB=jam_db
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U jammer -d jam_db -p 5432 -h localhost"] 
      interval: 10s
      retries: 5
      start_period: 30s
      timeout: 10s
  app:
    container_name: app
    build: .
    env_file:
      - .env
    environment:
       - DATABASE_URL="postgresql://jammer:${POSTGRES_PASSWORD}@jam_db:5432/jam_db"
    ports:
      - 8080:8080
    depends_on:
      jam_db:
        condition: service_healthy
        restart: true

docker file:

# Get started with a build env with Rust nightly
FROM rustlang/rust:nightly-bookworm as builder

# If you’re using stable, use this instead
# FROM rust:1.74-bullseye as builder

# Install cargo-binstall, which makes it easier to install other
# cargo extensions like cargo-leptos
RUN wget https://github.com/cargo-bins/cargo-binstall/releases/latest/download/cargo-binstall-x86_64-unknown-linux-musl.tgz
RUN tar -xvf cargo-binstall-x86_64-unknown-linux-musl.tgz
RUN cp cargo-binstall /usr/local/cargo/bin

# Install cargo-leptos
RUN cargo binstall cargo-leptos -y

# Add the WASM target
RUN rustup target add wasm32-unknown-unknown


# Make an /app dir, which everything will eventually live in
RUN mkdir -p /app
WORKDIR /app
COPY . .

ENV SQLX_OFFLINE=true
ENV LETPOS_WASM_OPT_VERSION=0.9.0
# RUN cargo sqlx prepare

# Build the app
RUN cargo leptos build --release -vv


FROM debian:bookworm-slim as runtime
WORKDIR /app
RUN apt-get update -y \
  && apt-get install -y --no-install-recommends openssl ca-certificates \
  && apt-get autoremove -y \
  && apt-get clean -y \
  && rm -rf /var/lib/apt/lists/*

# -- NB: update binary name from "leptos_start" to match your app name in Cargo.toml --
# Copy the server binary to the /app directory
COPY --from=builder /app/target/release/music_jam /app/

# /target/site contains our JS/WASM/CSS, etc.
COPY --from=builder /app/target/site /app/site

# Copy Cargo.toml if it’s needed at runtime
COPY --from=builder /app/Cargo.toml /app/


# Copy the migrations directory if it’s needed at runtime
COPY --from=builder /app/db/migrations /app/db/migrations

# Set any required env variables and
ENV RUST_LOG="info"
ENV RUST_BACKTRACE="full"
ENV LEPTOS_SITE_ADDR="0.0.0.0:8080"
ENV LEPTOS_SITE_ROOT="site"
EXPOSE 8080
# -- NB: update binary name from "leptos_start" to match your app name in Cargo.toml --
# Run the server
CMD ["/app/music_jam"]

[abonander]

My guess as to what going on is that your POSTGRES_PASSWORD needs to be URL-encoded. Are you actually passing it as part of the URL to psql or pasting it in at the prompt?

You can just URL-encode your password, but what we do for simplicity is just put the whole database URL (with encoded password) in a secret. That way it can be changed without modifying the deployment, and it's easier to get it later if you need to connect manually.

[KOEGlike]

I'm passing the whole url to psql, but i will try to encode the password. Thank you for the answer

[KOEGlike]

But when i run it with postgresql://jammer:example_password@localhost:5432/jam_db (this is the actual password and url) and run the program on my local machine (with the same docker postgres container, thats why localhost) it doesn't give a parsing error

[abonander]

Okay, looking closer it's not likely an issue with URL-encoding.

I'm still not sure exactly what's going wrong, but I can tell you your .env file is the wrong format. It's not a shell script, you don't need export before each variable. It's just a list of key-value pairs: https://docs.docker.com/reference/compose-file/services/#env_file-format

However, I think that would just give you a "wrong password" error if it fails to parse the .env file, because POSTGRES_PASSWORD would not be set.

My current best guess has to do with how you're actually passing DATABASE_URL to the service:

environment:
       - DATABASE_URL="postgresql://jammer:${POSTGRES_PASSWORD}@jam_db:5432/jam_db"

There's no indication in the docs that Docker Compose can handle a quoted value in this format. It only shows it handling quotes when using a regular YAML map: https://docs.docker.com/reference/compose-file/services/#environment

If we pass a URL wrapped in quotes to Url::parse(), we get the RelativeUrlWithoutABase error, whereas any other possible value of DATABASE_URL from what you've shown parses just fine (even some surprising ones): https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=7f375d4556ba6f76b23be814a800344c

[KOEGlike]

This is it, I just figured it out on my own, should have looked, I needed to remove the quotes from the compose file. Thanks for the assistance!!!