-
Notifications
You must be signed in to change notification settings - Fork 59
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
Keep/Remove Python dependent package: nfs-utils #121
Comments
|
@bgilbert Would be interested in filing a RFE bug against nfs-utils package? |
@sinnykumari You probably shouldn't wait for me. 🙂 |
RFE bug to make separate sub-package for Python utilities - https://bugzilla.redhat.com/show_bug.cgi?id=1667889 |
Latest nfs-utils package available in F30 includes a Python script nfsconvert.py which is required to convert deprecated sysconfig/nfs configuration into /etc/nfs.conf . |
thanks @sinnykumari - we can talk about this in the next meeting. |
We chatted about this in the community meeting yesterday and we decided to accept the proposal to make a nfs-utils-coreos package. There are still conversations going on in the BZ exploring possibilities, but in general a new package is acceptable. |
Update from BZ discussion: The nfs team created a nfs-utils-coreos package for us that just contains the nfs client. My action item is to find out if FCOS needs to ship the server or is just the client OK? Other open questions from the BZ:
|
Discussed in the meeting today. We agreed on the following statement:
|
FYI f30 and f31 rpm builds with nfs-utils-coreos rpm in them:
|
closed via coreos/fedora-coreos-config#84 |
@dustymabe , the predecessor of FCOS has NFS server included :/ Does anyone know a "stable" NFS-server container for FCOS? |
I don't know of one off hand. Anyone else? |
This might fall under #401. |
Here is a nfs-server contribution :) I've tried https://github.com/ehough/docker-nfs-server . The fcct for nfsv4: variant: fcos
version: 1.0.0
storage:
files:
- path: /etc/modules-load.d/nfs.conf
mode: 0660
contents:
inline: |
nfs
nfsd
systemd:
units:
- name: nfs-server.service
enabled: true
contents: |
[Unit]
Description=NFS Server
After=network-online.target
Wants=network-online.target
[Service]
Environment=REGISTRY_AUTH_FILE=<your path>/.docker/config.json
TimeoutStartSec=0
ExecStartPre=-/bin/podman kill nfs-server
ExecStartPre=-/bin/podman rm nfs-server
ExecStartPre=/bin/podman pull <your repos>
ExecStart=/bin/podman run --rm --name nfs-server \
--cap-add SYS_ADMIN --cap-add SYS_MODULE \
-e NFS_LOG_LEVEL=DEBUG \
-p 2049:2049 \
${data_volume_mounts} -v ${exports_file}:/etc/exports:Z -v /lib/modules:/lib/modules:ro --security-opt label=disable \
<your repos>
KillMode=none
Type=simple
[Install]
WantedBy=multi-user.target data_volume_mounts, exports_file, |
I think that FCOS should have a NFS server included in its base package. But I agree that having Python as a dependency for just a NFS server is ridiculous. |
this is going to be maintained by the FCOS team? I really need a permanent/stable nfs server solution for my FCOS deployments |
@diabl0w I think this is a good candidate for inclusion in the docs. However we cannot support container images that are not built in the Fedora ecosystem. If you can come up with a working fedora-container based Dockerfile, I'm happy to help you get it into Fedora's container registry. |
Thanks for the response, unfortunately I am not qualified to be doing that, haha. I've been just following the rabbit hole of a few issues being linked to running an nfs server inside coreos. It seems like the only solution for now is running a 3rd party container, until the nfs-server nfs-client rpms get sorted out. |
FCOS community members are trying not to ship Python in base system. In ticket #92, we have identified list of Python dependent packages which are currently installed in FCOS.
This ticket is to investigate that do we really need
nfs-utils
in FCOS base system? If yes, how can we providenfs-utils
or equivalent functionalities without shipping Python.The text was updated successfully, but these errors were encountered: