This seems like an awesome self hosting project - as such I wanted to trial running this in kubernetes (k3s) - I am trying to re-use a directory I already have for roms, but they do not seem to get picked up. I can upload roms successfully through the content management portal, and start a test uploaded rom from the webui. The local filesystem has permission set 777 for testing.
I am using line 80 of this readme to determine that presenting volumeMounts are possible.
Expected Behavior
The webui/content management ui should show all roms presented through the mounted volume.
Current Behavior
The webui/content managment ui show the volume names (snes and segaMD) as presented through the options given in the manifest, but do not show the local rom files, only uploaded roms.
OS: Linux
CPU architecture: x86_64
How docker service was installed:
OS provided
Command used to create docker container (run/create/compose/screenshot)
kubectl apply -f ./file.yaml
Docker logs
Nothing is logged to stdout of the pod - even if the content management page is successfully hit, so I am unsure if this is by design or a bug in the latest container.
Edit - looks like only ERRORS are logged to stdout. eg:
2022-09-18T18:19:25.443+1000 ERROR bitswap providerquerymanager/providerquerymanager.go:338 Received provider (12D3KooWGdc7YV8RzAoW58i8iVVS8MYruaNvB9MC8UTqxrXAT3Nh) for cid (QmTdEd9pcvb5AQp5iwLVb9LpogzSXWosYZFAJrj8n2G6qW) not requested
Additional question:
Can I present multiple volumeMounts that form part of the /data folder structure? Eg I would like to create a pvc for the downloading of the /data/main/* contents, and have that persist and be subsequently available to use for any replacement pod, but I would also want to present data/<emulator>/roms to the pod from my local file storage.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This seems like an awesome self hosting project - as such I wanted to trial running this in kubernetes (k3s) - I am trying to re-use a directory I already have for roms, but they do not seem to get picked up. I can upload roms successfully through the content management portal, and start a test uploaded rom from the webui. The local filesystem has permission set 777 for testing.
I am using line 80 of this readme to determine that presenting volumeMounts are possible.
Expected Behavior
The webui/content management ui should show all roms presented through the mounted volume.
Current Behavior
The webui/content managment ui show the volume names (snes and segaMD) as presented through the options given in the manifest, but do not show the local rom files, only uploaded roms.
Steps to Reproduce
Environment
OS: Linux CPU architecture: x86_64 How docker service was installed: OS provided
Command used to create docker container (run/create/compose/screenshot)
kubectl apply -f ./file.yaml
Docker logs
Nothing is logged to stdout of the pod - even if the content management page is successfully hit, so I am unsure if this is by design or a bug in the latest container.
Edit - looks like only
ERRORS
are logged to stdout. eg:Additional question: Can I present multiple volumeMounts that form part of the
/data
folder structure? Eg I would like to create a pvc for the downloading of the/data/main/*
contents, and have that persist and be subsequently available to use for any replacement pod, but I would also want to presentdata/<emulator>/roms
to the pod from my local file storage.