Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change logs and video volumes location #315

Open
benzman81 opened this issue Jul 19, 2022 · 0 comments
Open

Change logs and video volumes location #315

benzman81 opened this issue Jul 19, 2022 · 0 comments

Comments

@benzman81
Copy link

Currently, cm selenoid is started so that the mount for logs and video are subdirectories of the default configuration directory or the directory configured with --config-dir. Using rancher-desktop and WSL on windows this currently leads to a problem.

See issue here: rancher-sandbox/rancher-desktop#2574

Since I generally think, that it is a bad idea to mount a folder and also subfolders of this folder to other folders in the image, I would suggest a chanhe here.

For example, as of today, we mount ~/.aerokube/selenoid to /etc/selenoid and ~/.aerokube/selenoid/video to /opt/selenoid/video and ~/.aerokube/selenoid/logs to /opt/selenoid/logs. So within the docker image the following folders exist:

/etc/selenoid
/etc/selenoid/video
/etc/selenoid/logs
/opt/selenoid/video
/opt/selenoid/logs

You see, that the video and logs folders are available twice, which is unneccesary.
Not knowing the internal of the image I would suggest either a single mount ~/.aerokube/selenoid to /opt/selenoid and read/write configuration, video and logs within this folder, or create three mounts ~/.aerokube/selenoid/conf to /etc/selenoid for configuration, ~/.aerokube/selenoid/video to /opt/selenoid/video for video and ~/.aerokube/selenoid/logs to /opt/selenoid/logs for logs.

This would be much cleaner and by the way bypass the bug in rancher-desktop stated above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants