Thank you for the update
I was able to fix the issue once I change the ownership in smb server
now I am facing another issue
I was trying to create a container CT using this CIFS store (content rootdir,vztmpl,images,iso)but getting the following error
Job for
pve-container@204.service failed because the control process exited with error code.
See "systemctl status
pve-container@204.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@204' failed: exit code 1
systemctl status
pve-container@204.service
=======================================
●
pve-container@204.service - PVE LXC Container: 204
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-09-04 15:23:35 CEST; 17s ago
Docs: man:lxc-start
man:lxc
man
![Stick Out Tongue :p :p](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
ct
Process: 54970 ExecStart=/usr/bin/lxc-start -n 204 (code=exited, status=1/FAILURE)
Sep 04 15:22:36 stblade4 systemd[1]: Starting PVE LXC Container: 204...
Sep 04 15:23:35 stblade4 lxc-start[54970]: lxc-start: 204: lxccontainer.c: wait_on_daemonized_start: 856 No such file or directory - Failed to r
Sep 04 15:23:35 stblade4 lxc-start[54970]: lxc-start: 204: tools/lxc_start.c: main: 330 The container failed to start
Sep 04 15:23:35 stblade4 lxc-start[54970]: lxc-start: 204: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mod
Sep 04 15:23:35 stblade4 lxc-start[54970]: lxc-start: 204: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --
Sep 04 15:23:35 stblade4 systemd[1]:
pve-container@204.service: Control process exited, code=exited, status=1/FAILURE
Sep 04 15:23:35 stblade4 systemd[1]:
pve-container@204.service: Failed with result 'exit-code'.
Sep 04 15:23:35 stblade4 systemd[1]: Failed to start PVE LXC Container: 204.