When creating a PR environment with railway environment new <name> --copy <source-env>, service

configurations and variables are copied, but volumes are not created in the new environment.

This causes services that depend on $RAILWAY_VOLUME_MOUNT_PATH (like Redis) to crash because the

variable is empty, producing malformed config:

*** FATAL CONFIG FILE ERROR (Redis 8.6.0) ***

Reading the configuration file, at line 4

>>> 'dir "--loadmodule" "/usr/local/lib/redis/modules//redisbloom.so"'

wrong number of arguments

Reproduction:

1. Have a staging environment with a Redis service + volume mounted at /data

2. Run railway environment new pr-test --copy <staging-env-id>

3. Redis service in new environment has volumeMounts: [] — no volume created

4. $RAILWAY_VOLUME_MOUNT_PATH is empty, --dir gets no value, Redis fails to start

Expected behavior:

--copy should either:

- Also create volumes in the new environment (matching source mount paths)

- Or document that volumes are NOT copied, so users can add railway volume add as a post-creation

step

Workaround:

After creating the environment, manually add the volume:

railway volume add --mount-path /data --service Redis

Environment: Railway CLI v4.x, Redis 8.6.0 Docker image