Trying to install Pangolin, and diligently following the instructions. Everything seems to run OK until the post installation steps when I got the following error
Error response from daemon: error while creating mount source path '/opt/Pangolin/config': mkdir /opt/Pangolin: read-only file system
I can see that the three Docker containers have been created successfully. If I try to start the Pandolin container manually, I get the same error. The installer was run using sudo and /opt/Pangolin is owned by root and has user permissions. The config subfolder already exists
Any suggestions would be greatly appreciated!
Originally created by @alanarthur on GitHub (Apr 24, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/581
Hi,
Apologies in advance for my newbieness!
Trying to install Pangolin, and diligently following the instructions. Everything seems to run OK until the post installation steps when I got the following error
_Error response from daemon: error while creating mount source path '/opt/Pangolin/config': mkdir /opt/Pangolin: read-only file system_
I can see that the three Docker containers have been created successfully. If I try to start the Pandolin container manually, I get the same error. The installer was run using sudo and /opt/Pangolin is owned by root and has user permissions. The config subfolder already exists
Any suggestions would be greatly appreciated!
That looks like it means that Docker is trying to access or create /opt/Pangolin/config on your host system, but the filesystem is mounted as read-only, so Docker can’t create or write to that directory. You might want to look into creating a directory somewhere else like var or your home directory.
<!-- gh-comment-id:2826277318 -->
@miloschwartz commented on GitHub (Apr 24, 2025):
That looks like it means that Docker is trying to access or create /opt/Pangolin/config on your host system, but the filesystem is mounted as read-only, so Docker can’t create or write to that directory. You might want to look into creating a directory somewhere else like var or your home directory.
@github-actions[bot] commented on GitHub (May 9, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:2864858484 -->
@github-actions[bot] commented on GitHub (May 9, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (May 24, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
<!-- gh-comment-id:2906085679 -->
@github-actions[bot] commented on GitHub (May 24, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @alanarthur on GitHub (Apr 24, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/581
Hi,
Apologies in advance for my newbieness!
Trying to install Pangolin, and diligently following the instructions. Everything seems to run OK until the post installation steps when I got the following error
Error response from daemon: error while creating mount source path '/opt/Pangolin/config': mkdir /opt/Pangolin: read-only file system
I can see that the three Docker containers have been created successfully. If I try to start the Pandolin container manually, I get the same error. The installer was run using sudo and /opt/Pangolin is owned by root and has user permissions. The config subfolder already exists
Any suggestions would be greatly appreciated!
@miloschwartz commented on GitHub (Apr 24, 2025):
That looks like it means that Docker is trying to access or create /opt/Pangolin/config on your host system, but the filesystem is mounted as read-only, so Docker can’t create or write to that directory. You might want to look into creating a directory somewhere else like var or your home directory.
@github-actions[bot] commented on GitHub (May 9, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (May 24, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.