Having problem with the following issue: I don't know if I missed something, login as root and I should have all the write permissions.
---- installing extra_pkgs to the base env ----
conda-repo-cli-1.0.1+2.g39f4600-py_0.tar.bz2:
NotWritableError: The current user does not have write permissions to a required path.
path: /.conda/pkgs/urls.txt
uid: 0
gid: 100
If you feel that permissions on this path are set incorrectly, you can manually
change them by executing
$ sudo chown 0:100 /.conda/pkgs/urls.txt
Here is the log:
ROOT:/SYSTEM/var/minirun #>ls -la
total 158496
drwxrwxrwx 2 ROOT OMVS 8192 Oct 25 15:20 .
drwxrwxrwx 22 ROOT OMVS 8192 Oct 25 15:20 ..
-rw-r----- 1 ROOT OMVS 624 Oct 25 14:18 appdev_manifest_1.2.txt
-rwxr-x--x 1 ROOT OMVS 81071562 Oct 25 14:06 miniconda-zos-1.2.1-2020-12-23.run
ROOT:/SYSTEM/var/minirun #>./miniconda-zos-1.2.1-2020-12-23.run -p /var/miniconda
********************************************************************************
* Miniconda installation script is starting at 2021.10.25 15:21:00...
********************************************************************************
Installing Miniconda distribution to '/var/miniconda'. Continue? [Y/n] Y
Moving out sensitive files and directories...
Extracting packages from distribution...
Installing packages...
PREFIX=/SYSTEM/var/miniconda
installing: preconda ...
installing: anaconda-client-1.7.2-py37_2 ...
installing: asn1crypto-0.24.0-py37_0 ...
installing: autotag-0.5-10 ...
installing: bash-4.3.48-2 ...
installing: beautifulsoup4-4.6.0-py37_0 ...
installing: bzip2-1.0.6-6 ...
installing: certifi-2018.4.16-py37_0 ...
installing: cffi-1.11.5-py37_0 ...
installing: chardet-3.0.4-py37_0 ...
installing: click-6.7-py37_1 ...
installing: clyent-1.2.1-py37_1 ...
installing: conda-4.5.8-py37_11 ...
installing: conda-build-3.12.0-py37_5 ...
installing: conda-verify-3.0.2-py37_0 ...
installing: cryptography-2.3-py37_3 ...
installing: decorator-4.3.0-py37_0 ...
installing: filelock-3.0.4-py37_0 ...
installing: future-0.16.0-py37_1 ...
installing: gettext-0.19.8.1-1 ...
installing: glob2-0.6-py37_2 ...
installing: idna-2.7-py37_0 ...
installing: ipython_genutils-0.2.0-py37_0 ...
installing: jinja2-2.10-py37_0 ...
installing: jsonschema-2.6.0-py37_1 ...
installing: jupyter_core-4.4.0-py37_2 ...
installing: libffi-3.2.1-6 ...
installing: markupsafe-1.0-py37_5 ...
installing: nbformat-4.4.0-py37_0 ...
installing: ncurses-6.1-10 ...
installing: openssl-1.0.2k-5 ...
installing: pkginfo-1.4.2-py37_0 ...
installing: pyasn1-0.4.3-py37_0 ...
installing: pycosat-0.6.3-py37_0 ...
installing: pycparser-2.18-py37_0 ...
installing: pyopenssl-18.0.0-py37_2 ...
installing: python-3.7.0-30 ...
installing: python-dateutil-2.7.3-py37_0 ...
installing: pytz-2018.5-py37_0 ...
installing: pyyaml-3.13-py37_0 ...
installing: readline-7.0-3 ...
installing: requests-2.19.1-py37_0 ...
installing: ruamel_yaml-0.15.43-py37_0 ...
installing: setuptools-40.0.0-py37_0 ...
installing: six-1.14.0-py37_2 ...
installing: sqlite-3.23.1-0 ...
installing: traitlets-4.3.2-py37_1 ...
installing: urllib3-1.23-py37_0 ...
installing: xz-5.2.3-2 ...
installing: yaml-0.1.6-1 ...
installing: zlib-1.2.11-4 ...
Building the "base" Anaconda environment
Done.
---- installing extra_pkgs to the base env ----
conda-repo-cli-1.0.1+2.g39f4600-py_0.tar.bz2:
NotWritableError: The current user does not have write permissions to a required path.
path: /.conda/pkgs/urls.txt
uid: 0
gid: 100
If you feel that permissions on this path are set incorrectly, you can manually
change them by executing
$ sudo chown 0:100 /.conda/pkgs/urls.txt
In general, it's not advisable to use 'sudo conda'.
ROOT:/SYSTEM/var/minirun #>
------------------------------
Raymond Lam
developer
IBM Global Services
Endicott NY United States
------------------------------
Hi Raymond,
More likely, the root filesystem is mounted as read-only and it is a reason why conda cannot create a /.conda directory.
The root filesystems rights can be checked by the 'df -v /' command.
As a workaround, you can temporary set $HOME variable to your own home directory and install miniconda at the specified path:
export HOME=/u/<user>
./miniconda-zos-1.2.1-2020-12-23.run -p /var/miniconda
It's better to delete $HOME/.conda directory after the workaround way of installation, because the root rights can block the usage of conda by user whom home directory was used. Miniconda will restore this directory with proper access after start of using.
rm -rf $HOME/.conda
Thanks,
Sergey
------------------------------
Sergey Rezepin
Rocket Software
------------------------------
Hi Raymond,
More likely, the root filesystem is mounted as read-only and it is a reason why conda cannot create a /.conda directory.
The root filesystems rights can be checked by the 'df -v /' command.
As a workaround, you can temporary set $HOME variable to your own home directory and install miniconda at the specified path:
export HOME=/u/<user>
./miniconda-zos-1.2.1-2020-12-23.run -p /var/miniconda
It's better to delete $HOME/.conda directory after the workaround way of installation, because the root rights can block the usage of conda by user whom home directory was used. Miniconda will restore this directory with proper access after start of using.
rm -rf $HOME/.conda
Thanks,
Sergey
------------------------------
Sergey Rezepin
Rocket Software
------------------------------
Hi Sergey,
Thank you so much for your help; as you suggested I exported HOME=/u/user and ran the installation(see install.log) . Just to make sure I don't need to "Configure to use Rocket's secure conda serve". After that I tried to ran conda -V and it seems the conda command is not recognized (see profile.log).
My main goal of setting up miniconda is to install the latest Rocket GIT, please advise.
Building the "base" Anaconda environment
Done.
---- installing extra_pkgs to the base env ----
conda-repo-cli-1.0.1+2.g39f4600-py_0.tar.bz2:
Downloading and Extracting Packages
*-None | | ########## | 100%
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
Creating .condarc file...
Configure to use Rocket's secure conda server? [Y/n] n
Installation successful.
------------------------------
Raymond Lam
developer
IBM Global Services
Endicott NY United States
------------------------------
Hi Sergey,
Thank you so much for your help; as you suggested I exported HOME=/u/user and ran the installation(see install.log) . Just to make sure I don't need to "Configure to use Rocket's secure conda serve". After that I tried to ran conda -V and it seems the conda command is not recognized (see profile.log).
My main goal of setting up miniconda is to install the latest Rocket GIT, please advise.
Building the "base" Anaconda environment
Done.
---- installing extra_pkgs to the base env ----
conda-repo-cli-1.0.1+2.g39f4600-py_0.tar.bz2:
Downloading and Extracting Packages
*-None | | ########## | 100%
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
Creating .condarc file...
Configure to use Rocket's secure conda server? [Y/n] n
Installation successful.
------------------------------
Raymond Lam
developer
IBM Global Services
Endicott NY United States
------------------------------
Has to rename attached file:
install.log to install.txt
profile.log to profile.txt
------------------------------
Raymond Lam
developer
IBM Global Services
Endicott NY United States
------------------------------
Has to rename attached file:
install.log to install.txt
profile.log to profile.txt
------------------------------
Raymond Lam
developer
IBM Global Services
Endicott NY United States
------------------------------
Hi Raymond,
Miniconda needs to be run from bash and doesn't really support /bin/sh. In your logs, I don't see what shell you're using, but this error message indicates it's probably sh:
local: conda 4: FSUM7351 not found
Bash is shipped as a part of Miniconda (it lives in Miniconda's bin directory) so that you can start it before attempting to use conda itself.
Regards,
Vladimir
------------------------------
Vladimir Ein
Rocket Internal - All Brands
------------------------------
