When starting a container with dockerify in it I get the following error: dockerfy: 2017/03/31 10:54:56 Could not copy secrets files%!(EXTRA *os.PathError=mkdir /root/.secrets/: file exists)
I've tried an rm -rf on that folder as it's empty but that doesn't work.
The CMD in the Dockerfile is: ENTRYPOINT ["dockerfy", "--secrets-files", "/secrets/empty.env", "--start", "/bin/filebeat/filebeat -e -c /etc/filebeat/filebeat.yml", "--", "pm2-docker", "--json", "/opt/app/index.js"]. The /secrets/empty.env exists. I tried doing that to solve the error above but it didn't help.
The base image is node:6-alpine. Is it possible to have it not create the folder when it exists?
When starting a container with dockerify in it I get the following error:
dockerfy: 2017/03/31 10:54:56 Could not copy secrets files%!(EXTRA *os.PathError=mkdir /root/.secrets/: file exists)I've tried an rm -rf on that folder as it's empty but that doesn't work.
The CMD in the Dockerfile is:
ENTRYPOINT ["dockerfy", "--secrets-files", "/secrets/empty.env", "--start", "/bin/filebeat/filebeat -e -c /etc/filebeat/filebeat.yml", "--", "pm2-docker", "--json", "/opt/app/index.js"]. The /secrets/empty.env exists. I tried doing that to solve the error above but it didn't help.The base image is node:6-alpine. Is it possible to have it not create the folder when it exists?