A dirty workaround for potential permissions issue rooted in the fact that originally tftp server that hosts the SR OS config was run by the tftp user wity uid/gid = 103/106.
This caused access issues on some installations where SR OS was not able to save the config due to permissions error -- more in this discord thread.
It appears to be that the issue is amplifed by the File ACLs added in containerlab some time ago.
A dirty workaround for potential permissions issue rooted in the fact that originally tftp server that hosts the SR OS config was run by the
tftp
user wity uid/gid = 103/106.This caused access issues on some installations where SR OS was not able to save the config due to permissions error -- more in this discord thread. It appears to be that the issue is amplifed by the File ACLs added in containerlab some time ago.
The file ACLs for the tftboot dir are as follows:
It is not clear why these facls were a problem for some deployments, as I couldn't reproduce it on my VMs.
As a quick workaround the user has been changed from the
tftp
toroot
in the tftp server launch command, this should prevent potential access issues.