[OP Stack Deployment] op-deployer apply error

[Blue003-dev]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I am setting up l2 opchain locally while viewing the following page.
https://docs.optimism.io/operators/chain-operators/tutorials/create-l2-rollup

When I entered the following command, the following error occurred. Could you please help me resolve this issue?
./op-deployer apply --workdir .deployer
--l1-rpc-url https://XXXXX
--private-key XXXXX
Application failed: failed to download L1 artifacts: failed to download artifacts: failed to download artifacts: failed to download: failed to ensure cache directory: mkdir : no such file or directory

Below is the content of intent.toml in the .deployer folder.

configType = “standard”
l1ChainID = 11155111
fundDevAccounts = false
useInterop = false
l1ContractsLocator = ”tag://op-contracts/v3.0.0-rc.2”
l2ContractsLocator = “tag://op-contracts/v3.0.0-rc.2”

[superchainRoles]
proxyAdminOwner = ”0x1eb2ffc903729a0f03966b917003800b145f56e2”
protocolVersionsOwner = “0xfd1d2e729ae8eee2e146c033bf4400fe75284301”
guardian = ”0x7a50f00e8d05b95f98fe38d8bee366a7324dcf7e”

[[chains]]
id = “0x000000000000000000000000000000000000000000000000000000000000a455”
baseFeeVaultRecipient = “0x4222b904c199EA6F9D6c4a85f5DCf82F0FFd73AA”
l1FeeVaultRecipient = ”0x4222b904c199EA6F9D6c4a85f5DCf82F0FFd73AA”
sequencerFeeVaultRecipient = “0x4222b904c199EA6F9D6c4a85f5DCf82F0FFd73AA”
eip1559DenominatorCanyon = 250
eip1559Denominator = 50
eip1559Elasticity = 6
operatorFeeScalar = 0
operatorFeeConstant = 0
[chains.roles]
l1ProxyAdminOwner = “0x1eb2ffc903729a0f03966b917003800b145f56e2”
l2ProxyAdminOwner = “0x2fc3ffc903729a0f03966b917003800b145f67f3”
systemConfigOwner = ”0x4222b904c199EA6F9D6c4a85f5DCf82F0FFd73AA”
unsafeBlockSigner = “0x30a77384a6fCb9e3e882e820EDD8f77F68CE974f”
batcher = ”0xBc98dEd8E7e8e6750E4C3DE1831F4d8284d92Af7”
proposer = “0xe94D3e77816FCeFa541C4a82AE952C30471D6e1b”
challenger = ”0xfd1d2e729ae8eee2e146c033bf4400fe75284301”

Thank you. :) !

Logs

No response

Additional Information

No response

Feedback

No response

[opfocus]

./op-deployer apply --workdir .deployer try to use full path here, like /root/..../.deployer

[opfocus]

If this helpfull, you can mark it as the accepted answer (you can also mark your own answer as accepted), and then close the discussion.

[JamesSmartCell]

Same issue, I am using

~/dev/optimism$ ./op-deployer/op-deployer apply --workdir ~/dev/optimism/.deployer --l1-rpc-url https://1rpc.io/sepolia --private-key <MY_PRIVATE_KEY>

Are there any other suggestions? Could it be a misconfigured intent.toml? Like OP I am using the same recipient for base, vault and sequencer.

Could it be an RPC restriction? Should we be running a node?