[Application Development] <Title>

[rich-hyun]

Did you check the documentation?

• Yes
• No

Documentation Feedback (Optional)

Hi Optimism team/community,

I'm trying to run op-deployer apply using the official binary release of op-deployer v0.3.1 on Linux.

Despite setting the following environment variables:

export OP_DEPLOYER_CACHE_DIR=$(pwd)/op-cache
export OP_CACHE_DIR=$(pwd)/op-cache
and ensuring the directory structure exists:

./op-cache/
├── artifacts
│ ├── l1
│ │ └── genesis.json
│ ├── l2
│ │ └── genesis.json
│ └── tmp
I keep getting this error:

pgsql
복사
편집
Application failed: failed to download L1 artifacts: failed to ensure cache directory: mkdir : no such file or directory
I also used strace to trace the failing syscall, and saw that the mkdir call is attempting to create an empty path (i.e., mkdir "") which suggests that the environment variables are not being respected at all.

To debug further, I ran:

curl -s https://raw.githubusercontent.com/ethereum-optimism/optimism/op-deployer/v0.3.1/packages/op-deployer/fs/cache.go | grep -i cache_dir
→ and found no reference to OP_DEPLOYER_CACHE_DIR or OP_CACHE_DIR.

❓ My question:
Is v0.3.1 supposed to support OP_DEPLOYER_CACHE_DIR or any way to override the default cache path?

If not, is it safe to assume that only builds from main or newer versions (e.g. v0.3.3+) support this?

Is there a workaround for v0.3.1 other than creating /tmp/op-deployer-cache/artifacts/l1 manually?

Would you recommend using main branch instead of a versioned tag for better CLI support?

💡 Additional Context:
OS: Ubuntu 22.04

Shell: zsh

op-deployer version: v0.3.1 (from GitHub Releases)

Local test setup for custom L2 chain using op-node, op-geth, deployer

Thanks in advance for your guidance!

What type of issue are you experiencing?

• Error
• Feature Request
• General Question

Issue Description

up

Steps to Reproduce

up

Are you using a specific library or SDK?

• OP-SDK
• Viem
• Other
• Not Sure

Are you using the latest version of the library/SDK?

• Yes
• No

Environment Details

No response

Troubleshooting Attempts

No response

What type of support do you need?

• Technical support for issue resolution
• Feature implementation guidance
• General advice or consultation
• Documentation or learning resources

Additional Information

No response

Feedback

No response

[opfocus]

Is v0.3.1 supposed to support OP_DEPLOYER_CACHE_DIR or any way to override the default cache path?
Please check the help document to see if there is a flag for the environment variable you mentioned. If so, try using the flag.
Would you recommend using main branch instead of a versioned tag for better CLI support?
We should use version tags