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

[BUG] ServiceByName org.freedesktop.secrets runs into a timeout #18

Open
1 task done
IngwiePhoenix opened this issue Sep 5, 2024 · 4 comments
Open
1 task done

Comments

@IngwiePhoenix
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When attempting to connect to a MySQL server in the same docker-compose deployment, setting the password runs into this error:

image

The IPC lock cap is enabled.

Expected Behavior

I expected to save a password.

Steps To Reproduce

  1. Deploy
  2. Attempt to connect
  3. Observe the error

compose.yml:

services:
  wk:
    image: lscr.io/linuxserver/mysql-workbench:latest
    privileged: true
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Berlin
      - START_DOCKER=true
      - LC_ALL=de_DE.UTF-8
      - NO_DECOR=true
    volumes:
      - "./workbench:/config"
      #- "/var/run/docker.sock:/var/run/docker.sock"
      - "/dev/dri:/dev/dri"
    ports:
      - 3000:3000
      - 3001:3001
    cap_add:
      - IPC_LOCK
    restart: unless-stopped
  mysql:
    image: mysql:8.0-debian
    #command: mysqld --skip-ssl --sha256-password-auto-generate-rsa-keys=OFF --caching-sha2-password-auto-generate-rsa-keys=OFF
    volumes:
      - "mysql-data:/var/lib/mysql"
    environment:
      - "TZ=Europe/Berlin"
      - "MYSQL_ROOT_PASSWORD=thisisnotsafeandidontcare"
    ports:
      - "3306:3306"
    restart: unless-stopped

volumes:
  mysql-data:

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.
Copy link

github-actions bot commented Sep 5, 2024

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@j0nnymoe
Copy link
Member

j0nnymoe commented Sep 5, 2024

I wonder if it's a permissions issue on your /config volume for mysql-workbench.

@IngwiePhoenix
Copy link
Author

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).
image

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)

@LinuxServer-CI
Copy link
Collaborator

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.

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

No branches or pull requests

3 participants