You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reason for mysql-data is an annoying "bug" whereby permissions go all out of whack when mounting a local Windows folder through Podman, which runs in WSL. It's all over the place...
Environment
- OS: Windows 10
- How docker service was installed: Podman, docker-compose CLI. Deployment is above.
CPU architecture
x86-64
Docker creation
See above.
Container logs
None to note, the error is not logged.
The text was updated successfully, but these errors were encountered:
Given that I had one on the mysql one too, I'll try it.
Nope, same thing happened. I swapped the local folder (./workbench:/config) with a volume (workbench-data:/config).
Nothing in the log once again. Where would that service be "mounted"? Maybe I can see something when I pop a shell into the container. I usually use Linux for CLI, and if I do GUI, it's usually Wayland...and my dbus knowledge is pretty bad. x)
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Is there an existing issue for this?
Current Behavior
When attempting to connect to a MySQL server in the same docker-compose deployment, setting the password runs into this error:
The IPC lock cap is enabled.
Expected Behavior
I expected to save a password.
Steps To Reproduce
compose.yml
:Reason for
mysql-data
is an annoying "bug" whereby permissions go all out of whack when mounting a local Windows folder through Podman, which runs in WSL. It's all over the place...Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: