I am trying to install azure kinect on Ubuntu 18.04 following the instructions here https://scazlab.github.io/azure_setup_guide.html. I ran these lines of code
curl -sSL https://packages.microsoft.com/keys/microsoft.asc | sudo apt-key add -
sudo apt-add-repository https://packages.microsoft.com/ubuntu/18.04/prod
sudo apt-get update
and got the error message below
(base) kong#kong-Standard:~$ sudo apt-get update
Hit:1 http://ppa.launchpad.net/lutris-team/lutris/ubuntu bionic InRelease
Hit:2 http://packages.humanoids.kit.edu/bionic/main bionic InRelease
Hit:3 http://deb.anydesk.com all InRelease
Hit:4 http://packages.humanoids.kit.edu/bionic/testing bionic InRelease
Hit:5 https://packages.microsoft.com/ubuntu/18.04/prod bionic InRelease
Hit:6 http://gb.archive.ubuntu.com/ubuntu bionic InRelease
Hit:7 http://dl.google.com/linux/chrome/deb stable InRelease
Get:8 http://gb.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:9 http://gb.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:10 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Hit:11 http://packages.ros.org/ros/ubuntu bionic InRelease
Fetched 252 kB in 1s (220 kB/s)
Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://packages.microsoft.com/ubuntu/18.04/prod bionic InRelease' doesn't support architecture 'i386'
I found the solution to similar problem at this thread Skipping acquire of configured file 'main/binary-i386/Packages'
but in my case, I am not able to find the file /etc/apt/sources.list.d/bionic.list
In the folder /etc/apt/, where you have the folder source.list.d, you should also have a file called source.list.
Check if your package is there, and modify the corresponding line as needed.
cd /etc/apt/
cat sources.list
You should have a line like
https://packages.microsoft.com/ubuntu/18.04/prod bionic main somewhere probably towards the end.
Modify the file, using nano for example :
sudo nano sources.list
and add the mention [arch=amd64]:
deb [arch=amd64] https://packages.microsoft.com/ubuntu/18.04/prod bionic main
Related
I have a dynamic library that I want to use. However, one of its dependencies is not available on my system:
$ ldd redacted_name.so | grep 'not found'
libapt-pkg.so.5.0 => not found
I tried installing libapt-pkg, and it seemed to work. Here is the output for installing:
$ sudo apt install -y libapt-pkg5.0
Reading package lists... Done
Building dependency tree
apt apt-utils libapt-pkg6.0
3 upgraded, 0 newly installed, 0 to remove and 307 not upgraded.
Need to get 2346 kB of archives.
After this operation, 42.0 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libapt-pkg6.0 amd64 2.0.9 [839 kB]
Get:2 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 apt amd64 2.0.9 [1294 kB]
Get:3 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 apt-utils amd64 2.0.9 [213 kB]
Fetched 2346 kB in 2s (1474 kB/s)
(Reading database ... 54241 files and directories currently installed.)
Preparing to unpack .../libapt-pkg6.0_2.0.9_amd64.deb ...
Unpacking libapt-pkg6.0:amd64 (2.0.9) over (2.0.2) ...
Setting up libapt-pkg6.0:amd64 (2.0.9) ...
(Reading database ... 54241 files and directories currently installed.)
Preparing to unpack .../archives/apt_2.0.9_amd64.deb ...
Unpacking apt (2.0.9) over (2.0.2) ...
Setting up apt (2.0.9) ...
Removing obsolete conffile /etc/kernel/postinst.d/apt-auto-removal ...
(Reading database ... 54240 files and directories currently installed.)
Preparing to unpack .../apt-utils_2.0.9_amd64.deb ...
Unpacking apt-utils (2.0.9) over (2.0.2) ...
Setting up apt-utils (2.0.9) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.31-0ubuntu9) ...
Note that it says no packages were newly installed, and also note that it lists libapt-pkg6.0 in the output.
However, then I still see that the dependency is not found:
$ ldd redacted_name.so | grep 'not found'
libapt-pkg.so.5.0 => not found
Also, when I grep for my installed packages, libapt-pkg5.0 does not appear, but for some reason libapt-pkg6.0 does appear:
$ apt list --installed | grep libapt
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
libapt-pkg6.0/focal-updates,now 2.0.9 amd64 [installed]
If I try to install libapt-pkg5.0 again, it fails, mentioning that it is referred to by another package:
$ sudo apt install -y libapt-pkg5.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libapt-pkg5.0 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'libapt-pkg5.0' has no installation candidate
How can I correctly install libapt-pkg5.0 on my Ubuntu 20.04 system?
Previously, I had a fsx volume mounted on /shared directory.
However, Ubuntu 18.04 + fsx has some bug which causes reboot of the instance to unmount the fsx volume
Temporary solution:
Mount the fsx volume again
wget -O - https://fsx-lustre-client-repo-public-keys.s3.amazonaws.com/fsx-ubuntu-public-key.asc | sudo apt-key add -
sudo bash -c 'echo "deb https://fsx-lustre-client-repo.s3.amazonaws.com/ubuntu bionic main" > /etc/apt/sources.list.d/fsxlustreclientrepo.list'
sudo apt update -y
sudo apt install -y lustre-client-modules-$(uname -r)
sudo mount -t lustre -o noatime,flock fs-<id of the fsx>.fsx.us-east-1.amazonaws.com#tcp:/fsx /shared
ubuntu#<>:~$ ls /shared/
DeepLearningExamples checkpoint checkpoints checkpoints-1.data-00000-of-00001 checkpoints-1.index conda_tf25 conda_tf25_hvd deep-learning-models nccl_hosts
However, cleaner solution would not require this re-mounting of fsx volume after instance reboot.
I am trying to install ROS2 on Ubuntu 18.04.
The following command gives an error for not having the public key.
sudo apt update && sudo apt install curl gnupg2 lsb-release
Error:
Hit:1 http://ppa.launchpad.net/webupd8team/y-ppa-manager/ubuntu bionic InRelease
Hit:2 http://de.archive.ubuntu.com/ubuntu bionic InRelease
Hit:3 http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease
Get:4 http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:5 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:6 http://packages.ros.org/ros2/ubuntu bionic InRelease [2,565 B]
Err:6 http://packages.ros.org/ros2/ubuntu bionic InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5523BAEEB01FA116
Reading package lists... Done
W: GPG error: http://packages.ros.org/ros2/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5523BAEEB01FA116
E: The repository 'http://packages.ros.org/ros2/ubuntu bionic InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
I tried following ways to get the key:
sudo apt-key adv --keyserver ha.pool.sks-keyservers.net --recv-keys 5523BAEEB01FA116
and
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5523BAEEB01FA116
and y-ppa-manager ("Try to import all missing GPG keys")
sudo add-apt-repository ppa:webupd8team/y-ppa-manager
sudo apt-get install y-ppa-manager
y-ppa-manager
all the above methods give the following error
gpg: keyserver receive failed: No keyserver available
I am running Ubuntu 18.04 using a VM on a Windows 7 host.
How to avail the keyserver?
You can get a copy of the currently working key from the Dockerfile used for the nightly build of the osrf/ros2 Docker image: https://hub.docker.com/r/osrf/ros2/dockerfile
# setup ros2 keys
RUN apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys C1CF6E31E6BADE8868B172B4F42ED6FBAB17C654
It's not a future-proof solution though, because I was initially using a different key for ROS2 Crystal, and then that key suddenly stopped working (we also have our own regular builds) and I got the same error as you. It turns out I had to update our build with the new keys.
I think a better solution moving forward is to just use that pre-built ROS2 environment available as a Docker image. That way, the keys get updated when they update it.
docker pull osrf/ros2:nightly
I'm implementing encryption on my website. It's hosted on Google Appengine using PHP as the backend language. I'm using Let's encrypt for the encryption. My assumption is that Google Appengine is using a LAMP to make the website. I also assume that the type of Linux is Ubuntu. These assumptions are the basis on why I choose those options on this webpage. This leads me to believe that I should execute the following commands:
$ sudo apt-get update
$ sudo apt-get install software-properties-common
$ sudo add-apt-repository ppa:certbot/certbot
$ sudo apt-get update
$ sudo apt-get install python-certbot-apache
$ sudo certbot --apache
$ sudo certbot -a dns-plugin -i apache -d "*.example.com" -d example.com --server https://acme-v02.api.letsencrypt.org/directory
$ sudo certbot renew --dry-run
These commands can't be entered into the Google Cloud Bash though. I enter them into a dockerfile which looks like this:
FROM gcr.io/cloudshell-images/cloudshell:latest
# Add your content here
RUN apt-get update
RUN apt-get install software-properties-common
RUN add-apt-repository ppa:certbot/certbot
RUN apt-get update
RUN apt-get install python-certbot-apache
RUN certbot --apache
RUN certbot -a dns-google -i apache -d "*.danieljohndunevant.io" -d danieljohndunevant.io --server https://acme-v02.api.letsencrypt.org/directory
RUN certbot renew --dry-run
# To trigger a rebuild of your Cloud Shell image:
# 1. Commit your changes locally: git commit -a
# 2. Push your changes upstream: git push origin master
# This triggers a rebuild of your image hosted at https://gcr.io/bold-origin-211113/djdioo
# You can find the Cloud Source Repository hosting this file at https://source.developers.google.com/p/bold-origin-211113/r/djdioo
The tutorial for how to set up a docker file gives you the following command to execute in order to debug image that you're creating:
cloudshell env build-local
The full output when I execute the command is the following:
Sending build context to Docker daemon 50.18kB
Step 1/9 : FROM gcr.io/cloudshell-images/cloudshell:latest
---> 15c050b71ac4
Step 2/9 : RUN apt-get update
---> Running in 119e813f8183
Hit:1 http://storage.googleapis.com/bazel-apt stable InRelease
Ign:2 http://deb.debian.org/debian jessie InRelease
Get:3 http://security.debian.org/debian-security stretch/updates InRelease [94.3 kB]
Get:4 http://deb.debian.org/debian jessie-backports InRelease [166 kB]
Ign:5 http://deb.debian.org/debian stretch InRelease
Hit:6 http://packages.cloud.google.com/apt gcsfuse-stretch InRelease
Get:7 http://deb.debian.org/debian stretch-backports InRelease [91.8 kB]
Get:8 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB]
Hit:9 http://deb.debian.org/debian jessie Release
Get:10 https://download.docker.com/linux/debian stretch InRelease [39.5 kB]
Hit:11 http://deb.debian.org/debian stretch Release
Get:12 https://packages.microsoft.com/repos/microsoft-debian-stretch-prod stretch InRelease [2852 B]
Get:13 http://security.debian.org/debian-security stretch/updates/main Sources [181 kB]
Get:14 http://deb.debian.org/debian stretch-backports/main Sources.diff/Index [27.8 kB]
Get:15 http://deb.debian.org/debian stretch-backports/main amd64 Packages.diff/Index [27.8 kB]
Get:16 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-19-0221.46.pdiff [5029 B]
Get:17 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-19-2029.26.pdiff [923 B]
Get:18 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-20-0220.22.pdiff [243 B]
Get:19 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-20-1412.59.pdiff [853 B]
Get:20 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-20-2016.48.pdiff [6000 B]
Get:21 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-21-0211.44.pdiff [847 B]
Get:22 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-21-1411.16.pdiff [241 B]
Get:23 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-22-1416.48.pdiff [956 B]
Get:24 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-22-2010.06.pdiff [1531 B]
Get:25 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-23-0213.38.pdiff [882 B]
Get:26 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [452 kB]
Get:27 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-23-0807.47.pdiff [33 B]
Get:28 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-23-1412.59.pdiff [13.4 kB]
Get:29 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-23-2006.55.pdiff [2376 B]
Get:30 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-24-0212.43.pdiff [87 B]
Get:31 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-24-0807.15.pdiff [1087 B]
Get:32 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-24-1407.53.pdiff [33 B]
Get:33 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-18-2018.05.pdiff [1572 B]
Get:34 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-19-0812.57.pdiff [1684 B]
Get:32 http://deb.debian.org/debian stretch-backports/main Sources 2018-10-24-1407.53.pdiff [33 B]
Get:36 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-19-1413.02.pdiff [20.3 kB]
Get:37 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-20-0220.22.pdiff [1770 B]
Get:39 https://packages.microsoft.com/repos/microsoft-debian-stretch-prod stretch/main amd64 Packages [28.7 kB]
Get:40 http://deb.debian.org/debian stretch-updates/main Sources.diff/Index [5656 B]
Get:41 https://download.docker.com/linux/debian stretch/stable amd64 Packages [4783 B]
Get:42 http://deb.debian.org/debian stretch-updates/main amd64 Packages.diff/Index [5656 B]
Get:43 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-20-2016.48.pdiff [1319 B]
Get:44 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-21-0211.44.pdiff [4166 B]
Get:45 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-21-0807.48.pdiff [521 B]
Get:46 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-21-1411.16.pdiff [270 B]
Get:47 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-22-0209.19.pdiff [1657 B]
Get:48 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-22-2010.06.pdiff [810 B]
Get:49 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-23-0213.38.pdiff [2897 B]
Get:50 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-23-0807.47.pdiff [456 B]
Get:51 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-23-1412.59.pdiff [11.3 kB]
Get:52 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-24-0212.43.pdiff [2666 B]
Get:53 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-24-0807.15.pdiff [624 B]
Get:54 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-24-1407.53.pdiff [216 B]
Get:54 http://deb.debian.org/debian stretch-backports/main amd64 Packages 2018-10-24-1407.53.pdiff [216 B]
Get:55 http://deb.debian.org/debian stretch-updates/main Sources 2018-10-20-2016.48.pdiff [792 B]
Get:56 http://deb.debian.org/debian stretch-updates/main amd64 Packages 2018-10-20-2016.48.pdiff [1577 B]
Get:55 http://deb.debian.org/debian stretch-updates/main Sources 2018-10-20-2016.48.pdiff [792 B]
Get:56 http://deb.debian.org/debian stretch-updates/main amd64 Packages 2018-10-20-2016.48.pdiff [1577 B]
Fetched 1308 kB in 2s (479 kB/s)
Reading package lists...
---> d918ded6e546
Removing intermediate container 119e813f8183
Step 3/9 : RUN apt-get install software-properties-common
---> Running in 855a7668814a
Reading package lists...
Building dependency tree...
Reading state information...
software-properties-common is already the newest version (0.96.20.2-1).
The following packages were automatically installed and are no longer required:
libgoogle-perftools4 libtcmalloc-minimal4
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.
---> dd6e99aae634
Removing intermediate container 855a7668814a
Step 4/9 : RUN add-apt-repository ppa:certbot/certbot
---> Running in 66578e8dac00
This is the PPA for packages prepared by Debian Let's Encrypt Team and backported for Ubuntu(s).
More info: https://launchpad.net/~certbot/+archive/ubuntu/certbot
gpg: keybox '/tmp/tmp5au8x0v1/pubring.gpg' created
gpg: /tmp/tmp5au8x0v1/trustdb.gpg: trustdb created
gpg: key 8C47BE8E75BCA694: public key "Launchpad PPA for certbot" imported
gpg: Total number processed: 1
gpg: imported: 1
Warning: apt-key output should not be parsed (stdout is not a terminal)
gpg: no valid OpenPGP data found.
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
self.run()
File "/usr/lib/python3.5/threading.py", line 862, in run
self._target(*self._args, **self._kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 688, in addkey_func
func(**kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 386, in add_key
return apsk.add_ppa_signing_key()
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 273, in add_ppa_signing_key
cleanup(tmp_keyring_dir)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 234, in cleanup
shutil.rmtree(tmp_keyring_dir)
File "/usr/lib/python3.5/shutil.py", line 480, in rmtree
_rmtree_safe_fd(fd, path, onerror)
File "/usr/lib/python3.5/shutil.py", line 438, in _rmtree_safe_fd
onerror(os.unlink, fullname, sys.exc_info())
File "/usr/lib/python3.5/shutil.py", line 436, in _rmtree_safe_fd
os.unlink(name, dir_fd=topfd)
FileNotFoundError: [Errno 2] No such file or directory: 'S.gpg-agent.extra'
---> f0b11dadc6de
Removing intermediate container 66578e8dac00
Step 5/9 : RUN apt-get update
---> Running in f913cd006561
Hit:1 http://storage.googleapis.com/bazel-apt stable InRelease
Hit:2 http://security.debian.org/debian-security stretch/updates InRelease
Ign:3 http://deb.debian.org/debian jessie InRelease
Hit:4 http://deb.debian.org/debian jessie-backports InRelease
Ign:5 http://deb.debian.org/debian stretch InRelease
Hit:6 http://deb.debian.org/debian stretch-backports InRelease
Hit:7 http://deb.debian.org/debian stretch-updates InRelease
Hit:8 http://deb.debian.org/debian jessie Release
Hit:9 http://deb.debian.org/debian stretch Release
Hit:10 http://packages.cloud.google.com/apt gcsfuse-stretch InRelease
Ign:11 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic InRelea
se
Hit:12 https://download.docker.com/linux/debian stretch InRelease
Hit:13 https://packages.microsoft.com/repos/microsoft-debian-stretch-
prod stretch InRelease
Ign:14 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic Release
Ign:15 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic/main am
d64 Packages
Ign:17 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic/main al
l Packages
Ign:15 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic/main am
d64 Packages
Ign:17 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic/main al
l Packages
Ign:15 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic/main am
d64 Packages
Ign:17 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic/main al
l Packages
Ign:15 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic/main am
d64 Packages
Ign:17 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic/main al
l Packages
Ign:15 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic/main am
d64 Packages
Ign:17 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic/main al
l Packages
Err:15 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic/main am
d64 Packages
404 Not Found
Ign:17 http://ppa.launchpad.net/certbot/certbot/ubuntu cosmic/main al
l Packages
Reading package lists...
W: The repository 'http://ppa.launchpad.net/certbot/certbot/ubuntu co
smic Release' does not have a Release file.
E: Failed to fetch http://ppa.launchpad.net/certbot/certbot/ubuntu/di
sts/cosmic/main/binary-amd64/Packages 404 Not Found
E: Some index files failed to download. They have been ignored, or ol
d ones used instead.
The command '/bin/sh -c apt-get update' returned a non-zero code: 100
I near the end of the output you can see the 404 error and the error code: 100. Thanks for reading. Hope one of you can come up with a solution.
Google do provide the managed SSL solution using Let's Encrypt with auto-renewal.
https://cloud.google.com/load-balancing/docs/ssl-certificates#managed-certs
What was the reason that you have to manage this on your own?
I'm trying to install MSSQL # Ubuntu 16.04 (as recommended # https://learn.microsoft.com/en-US/sql/linux/quickstart-install-connect-ubuntu?view=sql-server-linux-2017)
But that's the error I'm currently facing E: Unable to locate package mssql-server
test#test-VirtualBox:~$ wget -qO- https://packages.microsoft.com/keys/microsoft.asc | sudo apt-key add -
OK
test#test-VirtualBox:~$ sudo add-apt-repository "$(wget -qO- https://packages.microsoft.com/config/ubuntu/16.04/mssql-server-2017.list)"
test#test-VirtualBox:~$ sudo apt-get update
Hit:1 http://pl.archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://pl.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:3 http://pl.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:5 https://packages.microsoft.com/ubuntu/16.04/mssql-server-2017 xenial InRelease
Reading package lists... Done
test#test-VirtualBox:~$ sudo apt-get install -y mssql-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package mssql-server
What I'm doing wrong?
I've been trying many various Google queries like unable to locate package *mssql-server* site:github.com but nothing really solves my problem.
Thanks in advance
You may need to check whether the Ubuntu installed in your virtual machine is 32-bit or 64-bit. The packages for mssql-server are 64-bit only, and will be ignored on a 32-bit install.
check whether the Ubuntu installed in your virtual machine is 32-bit or 64-bit or ARM The packages for mssql-server are 64-bit only and it wont works with any ARM or 32 bit