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.

Sign up for GitHub

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

Jump to bottom

Solace Dev service doesn't need to set cpuset and ulimits, which may not work with some container runtimes #55

Closed
ozangunalp opened this issue Feb 6, 2024 · 3 comments · Fixed by #62
Closed

Solace Dev service doesn't need to set cpuset and ulimits, which may not work with some container runtimes #55

ozangunalp opened this issue Feb 6, 2024 · 3 comments · Fixed by #62

Comments

@ozangunalp
Copy link
Collaborator

Mentioned here: quarkusio/quarkus#37743 (comment)
@ozangunalp
Copy link
Collaborator Author

There seems to be other problems related to podman suppport : https://docs.solace.com/Software-Broker/SW-Broker-Set-Up/Containers/Set-Up-Podman-Container-Ubuntu.htm

I think it'll be difficult to make it work on podman.

@SravanThotakura05
Copy link
Collaborator

@ozangunalp when you say other problems are you referring to running the container with specific UID 1000 or different ones?

@ozangunalp
Copy link
Collaborator Author

Running the container with a specific uid doesn't resolve the issue with podman. It appears Solace needs specific rights to its working directory.

@ozangunalp ozangunalp mentioned this issue Feb 13, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Run solace container with a non-root user for podman compatibility ozangunalp/solace-quarkus
2 participants
@ozangunalp @SravanThotakura05