You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a container is run with -v /home/ftps/vsftpd-conf/:/etc/vsftpd/ a folder with all the config file get created but the file vsftpd.conf is empty. As the container attempt to start the Variables set at container runtime section gets populated but the container crashes as the rest of the config file is missing.
I was able to start the container by editing the config file and restart.
Every time I restart the container all Variables set at container runtime are duplicated ( the file grows at each restart ).
The text was updated successfully, but these errors were encountered:
I worked around the problem by copying the vsftpd.conf file back from a container created without the bind mount.
Then I launched the container with the bind mount and provided the customized conf file from the host.
Everything is working, the only problem is the vsftpd.conf file keep growing as runtime variables are appended on bottom at some intervals ( not only container restarts I suppose)
If a container is run with -v /home/ftps/vsftpd-conf/:/etc/vsftpd/ a folder with all the config file get created but the file vsftpd.conf is empty. As the container attempt to start the Variables set at container runtime section gets populated but the container crashes as the rest of the config file is missing.
I was able to start the container by editing the config file and restart.
Every time I restart the container all Variables set at container runtime are duplicated ( the file grows at each restart ).
The text was updated successfully, but these errors were encountered: