Open Toshibuck opened 7 months ago
If there is no way for the app to use /config
instead, then yes the other approach is to create (from Dockerfile) a symlink at /app
that points to /config
.
Hello,
I changed the path to /config in both the Dockerfile and startapp.sh, but I encountered an error stating that there was nothing in the directory during docker run. It's possible that the /config directory is created once the image is loaded. Consequently, I placed the application in /config on the volume side, and it worked. It's not an ideal solution, but it suits my needs.
However, the application requires a port. Do I need to specify a port somewhere? Considering that I'm routing this Docker through Gluetun, and I've properly opened the port in Gluetun, and there is indeed a VPN IP within the Docker I've created.
Thank you
I'm using your baseimage Docker to containerize the Ratioghost application. I can access the Ratioghost interface through the browser without any issue. However, the application saves its settings in a file which gets deleted every time the Docker is restarted because it's stored in the directory /app/ratioghost-master/. How can I work around this problem? Should I create a symbolic link between the /app and /config directories to make the data persistent?
Voici le dockerfile :
Et le start.sh:
I want to emphasize that I'm a complete beginner in creating Docker images, and I'm likely approaching it quite clumsily.
Thank you, Toshibuck.