Closed mdahshan closed 1 month ago
Hi
what are the original permissions on the ./vsftpd.conf
in your directory?
ls -la vsftpd.conf
The permissions in both machines are:
-rw-r--r-- 1 mostafa mostafa 88 Sep 19 10:31 vsftpd.conf
$ echo $UID
1000
Both machines are running Debian 12. The one that works fine is running on UTM on Apple Silicon.
$ docker exec clab-netfor3-ftpserver ls -l /etc/vsftpd/
total 4
-rw-r--r-- 1 root root 88 Sep 19 00:31 vsftpd.conf
The second one is on lib-virt on amd64. I also tested on Ubuntu 24.04 and I encountered the same issue. The ftpserver container refuses to start. When I changed the startup command and listed the directory content, I got 1000 1000 as owner and group.
your uid/gid is 1000, docker mounts the files with the same permissions you can
chmod
your conf file to 777 if you wish and then vsftpd should be able to use it.This is not something that containerlab controls.
Thanks for your help. I will do that.
Hi Team,
I am having an issue with the bind option for the node kind.
For the following topology:
When deploying the topology, the file vsftpd.conf has owner:group as 1000:1000 instead of the root. This breaks the functionality of the vsftpd as it refuses to start due to incorrect owner.
This problem only happens on the amd64 version. The arm64 version mounts correctly with root ownership.
Containerlab version:
The Dockerfile for ftpservers looks as follows:
Thanks for your help