Open SimoneGuarneri opened 2 years ago
Running into this too when trying to use with GitPod
Same here when trying to use the following devcontainer:
{
"name": "nfcore",
"image": "nfcore/gitpod:2.7.1",
"postCreateCommand": "bash .devcontainer/setup.sh",
"remoteUser": "gitpod",
"customizations": {
"vscode": {
"settings": {
"python.defaultInterpreterPath": "/opt/conda/bin/python",
"python.linting.enabled": true,
"python.linting.pylintEnabled": true,
"python.formatting.autopep8Path": "/opt/conda/bin/autopep8",
"python.formatting.yapfPath": "/opt/conda/bin/yapf",
"python.linting.flake8Path": "/opt/conda/bin/flake8",
"python.linting.pycodestylePath": "/opt/conda/bin/pycodestyle",
"python.linting.pydocstylePath": "/opt/conda/bin/pydocstyle",
"python.linting.pylintPath": "/opt/conda/bin/pylint"
},
"extensions": ["ms-python.python", "ms-python.vscode-pylance", "REditorSupport.r", "EditorConfig.EditorConfig",
"codezombiech.gitignore", "Gruntfuggly.todo-tree", "ms-vsliveshare.vsliveshare",
"nextflow.nextflow", "redhat.vscode-yaml", "streetsidesoftware.code-spell-checker"]
}
},
"features": {
"ghcr.io/devcontainers/features/docker-in-docker:2": {
"version": "latest"
},
"ghcr.io/devcontainers/features/aws-cli:1": {
"version": "latest"
}
}
}
My install log:
Performing compatibility checks
Executing https://repo.fig.io/scripts/apt/install.sh
Installing repo dependencies
Reading package lists... Done
Building dependency tree
Reading state information... Done
lsb-release is already the newest version (11.1.0ubuntu2).
lsb-release set to manually installed.
ca-certificates is already the newest version (20211016ubuntu0.20.04.1).
gnupg is already the newest version (2.2.19-3ubuntu2.2).
0 upgraded, 0 newly installed, 0 to remove and 102 not upgraded.
Installing Fig repository
Installing Fig key
gpg: WARNING: unsafe ownership on homedir '/home/gitpod/.gnupg'
Updating apt
Hit:1 https://download.docker.com/linux/ubuntu focal InRelease
Get:2 https://repo.fig.io/apt stable InRelease [2,438 B]
Hit:3 https://packages.microsoft.com/repos/microsoft-ubuntu-focal-prod focal InRelease
Hit:4 https://downloads.1password.com/linux/debian/amd64 stable InRelease
Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease
Hit:6 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:7 http://ppa.launchpad.net/git-core/ppa/ubuntu focal InRelease
Get:8 https://repo.fig.io/apt stable/main amd64 Packages [522 B]
Hit:9 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:10 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Fetched 2,960 B in 2s (1,805 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
102 packages can be upgraded. Run 'apt list --upgradable' to see them.
Installing Fig
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
fig-headless
0 upgraded, 1 newly installed, 0 to remove and 102 not upgraded.
Need to get 77.7 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://repo.fig.io/apt stable/main amd64 fig-headless amd64 2.13.1 [77.7 MB]
Fetched 77.7 MB in 2s (34.1 MB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package fig-headless.
(Reading database ... 36196 files and directories currently installed.)
Preparing to unpack .../fig-headless_2.13.1_amd64.deb ...
Unpacking fig-headless (2.13.1) ...
Setting up fig-headless (2.13.1) ...
Installing integrations
Installing dotfiles integration
Installed!
Installing daemon integration
error: Unsupported init system: <unknown>
Also have the same issue when installing fig on wsl 2
I initially had the same issue too. What fixed the issue for me was to set the init system to systemd
by doing the following:
wsl --update
/etc/wsl.conf
and added the following to it:[boot]
systemd=true
wsl.exe --shutdown
Prior to that I had tried to uninstall and re-install WSL, made sure it was set to WSL2 by entering in Powershell wsl --set-default-version 2
, and then re-installed Ubuntu but that didn't work. I also had to do a kernel update from Microsoft during this time that can be obtained here: https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel
Thanks a lot! after the same installation error "Unsupported init system" on WSL2 with Ubuntu 20.04.5 LTS ... i learned again... keep everything updated.
Steps 1 to 4 did it for me, and of course, Step 4 should fired inside your fresh updated wsl2 Distro.
Checks
fig doctor
in the affected terminal sessionfig restart
and replicated the issue againOperating system
Ubuntu (WSL)
Expected behaviour
fig starting
Actual behaviour
fig not starting due an error
Steps to reproduce
No response
Environment