Can --opt filename= include a path?

[pstieber]

Is it reasonable to specify the following?
buildctl build --frontend=dockerfile.v0 --local context=. --local dockerfile=. --opt filename=docker/Dockerfile
Also does this have any affect on pulled or pushed images using the following?
--output type=image,\"name=${REGISTRY_PATH}:latest,${REGISTRY_PATH}:ci-${CI_PIPELINE_ID}\",push=true
--export-cache type=inline
--import-cache type=registry,ref=${REGISTRY_PATH}:latest

[pstieber]

I'm asking because when I change from --local dockerfile=./docker --opt filename=Dockerfile to --local dockerfile=. --opt filename=docker/Dockerfile I get an error pushing the image:

#18 pushing layers 0.1s done
#18 ERROR: failed to push SCRUBBED_IMAGE_NAME: server message: insufficient_scope: authorization failed
------
 > importing cache manifest from SCRUBBED_IMAGE_NAME:
------
------
 > exporting to image:
------
error: failed to solve: failed to push SCRUBBED_IMAGE_NAME: server message: insufficient_scope: authorization failed

I don't understand the connection between my change and anything related to authorization. I can't tell if I should create an issue or if I'm doing something that is stupid.