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
Podman on systems with SELinux needs a :z or :Z suffix #8
Comments
I'm enjoying using Partkeepr in general. I feel that it really helping me organize my food better, I'm up to 53 different types of food and 83 items. Maybe someday I'll be able to integrate it into a recipe cookbook like NextCloud Cookbook but that's still sky-high on my wish list. I have yet to deploy it in a container as I want more experience before doing that. I'm using a Debian 9 (Stretch) VM for exploration into Partkeepr for now. Regarding risk management, my impression is that Alpine 3.10.3 is unfavorable.
What should I do about that? One possibility that I could work on to improve things slightly is to update from Alpine 3.10.3 to 3.10.9. That would entail extracting an old version from the Docker Library for PHP and updating that Dockerfile. Once the updated image is hosted this update would only need to be done once as there are no more Alpine 3.10.X updates. The other thing that comes to mind quickly is to switch to Debian 9 with Extended LTS support. That would be more work and would still have PHP 7.1 which is required due to being on Symphony 2. It might be the very best thing to become a Partkeepr contributor and work on migrating to Symphony 6. That would take me the most effort. |
Thanks a lot for your feedback! I will probably update the Dockerfile at some point to include an updated Alpine version. At the moment Partkeepr is being rewritten, see partkeepr/PartKeepr#1239. That means in the near future this image might not be necessary any more to run Partkeepr. Also if you are looking for an inventory system for food, grocy might be the better (and more modern) choice. |
Thanks for the tip about grocy. I do dread having to enter 174 different types of items and so on. I will take a look at it to see if it has all the features that I'm using now. Meanwhile I've updated Debian 9 (Squeeze) which comes with PHP 7.0.33-0+deb9u12 using the Freexian ELTS. Freexian is also on the Debian Gitlab instance. It provided me with 33 package updates.
Ubuntu 22.04 may be viable using PPAs It is easy for me to copy the database and data files from one test VM to another.
|
I finally got grocy installed despite the lack of documentation. I know I could have used a container but a friend of mine told me he always installs a package from scratch to see if how easy it is to install it. Packages that are not easy to install are a bad sign. Now I can't find a way to have nested Food Groups in grocy like I can in PartKeepr. I got PartKeepr to install on Ubuntu 22.04. |
Hello to you!
Thanks for working on this! I can't wait to deploy it. I'm new to PartKeepr but I've been using computers for 45 years now.
Today I wanted a way of keeping track of the food in my home because I'm forgetting what I have and can't plan to make recipes. I went poking around and I found PartKeepr and I immediacy wanted it in a virtual machine or a container or a snap for risk reduction (A.K.A "security" but my mindset is that "security" is not the best term for protection as it implies false things so I use "risk reduction" instead).
During my initial review (reading the README.md) I noticed that the volume names do that have the SELinux suffix. I will try to make a pull request when I am able so this is a notice about this issue.
For more information about SELinux Podman volume suffixes pleas see the Red Hat blog. Note that SELinux may be in use outside of Red Hat, for instance Android uses it too and probably others. There may be other issues with namespaces when using rootless Podman too.
https://www.redhat.com/sysadmin/user-namespaces-selinux-rootless-containers
The text was updated successfully, but these errors were encountered: