Does lxc creates /sys/fs/cgroup/memory/ *?

I am observing/suspecting a race condition while starting the lxc, sometime its start correctly, sometimes not, After seeing the log, concluded that not able to create the complete/correct path. because of that not able to start.

lxc-start workpath 20221207152206.395 TRACE cgfsng - cgfsng.c:cg_legacy_set_data:2324 - [DBG] cg_legacy_set_data : file_exists(/sys/fs/cgroup/memory/) = 1
lxc-start workpath 20221207152206.395 TRACE cgfsng - cgfsng.c:cg_legacy_set_data:2325 - [DBG] cg_legacy_set_data : file_exists(/sys/fs/cgroup/memory/lxc.payload/ = 0
lxc-start workpath 20221207152206.395 TRACE cgfsng - cgfsng.c:cg_legacy_set_data:2326 - [DBG] cg_legacy_set_data : file_exists(/sys/fs/cgroup/memory/lxc.payload/workpath/) = 0
lxc-start workpath 20221207152206.395 TRACE cgfsng - cgfsng.c:cg_legacy_set_data:2327 - [DBG] cg_legacy_set_data : file_exists(/sys/fs/cgroup/memory//lxc.payload/workpath/memory.limit_in_bytes) = 0
lxc-start workpath 20221207152206.395 TRACE cgfsng - cgfsng.c:cg_legacy_set_data:2328 - [DBG] cg_legacy_set_data : lxc_write_to_file /sys/fs/cgroup/memory//lxc.payload/workpath/memory.limit_in_bytes 1280M = -1
lxc-start workpath 20221207152206.395 WARN cgfsng - cgfsng.c:__cg_legacy_setup_limits:2362 - Failed to set “memory.limit_in_bytes” to “1280M”

I am new to lxc, do not have any idea about it.
I was suspecting that “/sys/fs/cgroup” created by the filesystem. am I correct?

Can someone please explain me the below points:

  1. what is the creation sequence?
  2. What could be the reason to not create the correct path?
    Or any suggestion to move ahead on this.

Thanks
Raj Kishor