Add LXD dependency on network filesystem

I have set up LXD on a Debian 10 using SNAP. The default storage pool source is /srv/lxd/default which is the mount point of a filesystem which requires network in order to mount. I have a container with the boot.autostart option set to true, but LXD fails to start the contaniner with this message:

Oct 07 18:46:59 HostServer lxd.daemon[1448]: t=2020-10-07T18:46:59+0200 lvl=eror msg="Failed to start instance 'container1': Common start logic: Failed tostart instance 'container1': Common start logic: Failed to create mount directory "/var/snap/lxd/common/lxd/storage-pools/default/containers/container1": mkdir /var/snap/lxd/common/lxd/storage-pools/default/containers/container1: no such file or directory"

I can start the container manually after boot using lxc start container1.

This is my storage list:

lxc storage list
+---------+-------------+--------+------------------+---------+
|  NAME   | DESCRIPTION | DRIVER |      SOURCE      | USED BY |
+---------+-------------+--------+------------------+---------+
| default |             | dir    | /srv/lxd/default | 2       |
+---------+-------------+--------+------------------+---------+

I wonder why LXD is trying to create mount directory on /var/snap/lxd/common/lxd/storage-pools/default/containers/container1 when the pool source is /srv/lxd/default. I think it maybe could be doing this because the filesystem is not ready at that point.

proc                    /proc                   proc    defaults                        0       0
/dev/mapper/root        /                       ext4    errors=remount-ro               0       1
/dev/mapper/vdd1_luks   /srv/lxd/default        ext4    errors=remount-ro,_netdev       0       2

Should I make the snap.lxd.daemon dependent on remote-fs.target?

Regards,