rootfs
commented
8 years ago how about running container in privileged mode?
Open abourget opened 8 years ago
rootfs
commented
8 years ago how about running container in privileged mode?
sunsided
commented
8 years ago Same problem here; tried using fedora:24 as well (and had to install nfs-ganesha-gluster to make it work at all), but nothing helped. Privileged mode didn't help either.
nfs-ganesha-1[main] main :MAIN :EVENT :nfs-ganesha Starting: Ganesha Version /builddir/build/BUILD/nfs-ganesha-2.4-dev-27/src, built at Aug 1 2016 17:56:07 on
nfs-ganesha-1[main] nfs_set_param_from_conf :NFS STARTUP :EVENT :Configuration file successfully parsed
nfs-ganesha-1[main] init_server_pkgs :NFS STARTUP :EVENT :Initializing ID Mapper.
nfs-ganesha-1[main] init_server_pkgs :NFS STARTUP :EVENT :ID Mapper successfully initialized.
nfs-ganesha-1[main] export_defaults_display :CONFIG :EVENT :DEFAULTS Export Defaults (root_squash , ----, 34-, UDP, TCP, ----, No Manage_Gids, -- Deleg, anon_uid= -2, anon_gid= -2, none, sys)
nfs-ganesha-1[main] export_defaults_display :CONFIG :EVENT :RESULT Export Defaults (root_squash , ----, 34-, UDP, TCP, ----, No Manage_Gids, -- Deleg, anon_uid= -2, anon_gid= -2, none, sys)
nfs-ganesha-1[main] glusterfs_create_export :FSAL :EVENT :Volume elasticsearch exported at : '/'
nfs-ganesha-1[main] lower_my_caps :NFS STARTUP :EVENT :CAP_SYS_RESOURCE was successfully removed for proper quota management in FSAL
nfs-ganesha-1[main] lower_my_caps :NFS STARTUP :EVENT :currenty set capabilities are: = cap_chown,cap_dac_override,cap_dac_read_search,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_linux_immutable,cap_net_bind_service,cap_net_broadcast,cap_net_admin,cap_net_raw,cap_ipc_lock,cap_ipc_owner,cap_sys_module,cap_sys_rawio,cap_sys_chroot,cap_sys_ptrace,cap_sys_pacct,cap_sys_admin,cap_sys_boot,cap_sys_nice,cap_sys_time,cap_sys_tty_config,cap_mknod,cap_lease,cap_audit_write,cap_audit_control,cap_setfcap+eip
nfs-ganesha-1[main] gsh_dbus_pkginit :DBUS :CRIT :dbus_bus_get failed (Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory)
nfs-ganesha-1[main] gsh_dbus_register_path :DBUS :CRIT :dbus_connection_register_object_path called with no DBUS connection
nfs-ganesha-1[main] gsh_dbus_register_path :DBUS :CRIT :dbus_connection_register_object_path called with no DBUS connection
nfs-ganesha-1[main] nfs_Init_svc :DISP :CRIT :Cannot acquire credentials for principal nfs
nfs-ganesha-1[main] Register_program :DISP :FATAL :Cannot register NFS V3 on UDP
nfs-ganesha-1[main] unregister_fsal :FSAL :CRIT :Unregister FSAL GLUSTER with non-zero refcount=2
nfs-ganesha-1[main] glusterfs_unload :FSAL :CRIT :FSAL Gluster unable to unload. Dying ...likely rpcbind is not started, added readme for help. thanks for testing.
jamshid
commented
7 years ago So rpcbind has to be running on the docker server itself? It's supposed to already be running on Mac? Though I don't know Docker for Mac can access the OSX rpcbind.
Anyway, starting rpcbind does not seem to fix this issue on a docker server running on Ubuntu 16. I verified with ps auxwf that rpcbind is running (/sbin/rpcbind -f -w).
PS: I guess running rpcbind has security concerns, starting it shows this scary warning.
username@61:~$ systemctl start rpcbind
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to start 'rpcbind.service'.
Authenticating as: <username>,,, (<username>)
Password:
==== AUTHENTICATION COMPLETE ===Are you running as root? For warning message might be asking you to sudo.
This is the logs output of what I get merely by executing this container with:
Logs:
Does it require
dbusnow ? is it a new dependency from when this was created ?