May 6, 2018 at 9:06 am
Banging my head on this one as I cannot find a way to install SQL Server on one of my laptops which I just upgraded to Ubuntu 18.04. I've checked all the M$ repositories and only the 16.04 is valid, the others are just skeletons.
😎
What I'm getting is this:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies.
mssql-server : Depends: openssl (<= 1.1.0)
Conflicts: mssql-server-agent but 14.0.3015.40-1 is to be installed
mssql-server-ha : Depends: resource-agents but it is not going to be installed
mssql-server-is : Depends: openssl (< 1.1.0)
E: Unable to correct problems, you have held broken packages.
Might have to downgrade the OS to 17.04 but I really would like to avoid doing that.
May 6, 2018 at 10:13 am
I had no luck either I'm afraid Eirikur. It seems that, at the moment, SQL Server 2017 on Linux doesn't support OpenSSL 1.1.0g (which is odd, as to me that's version <=1.1.0 still, unless anything after the original is no good). I had a look at the versions available on 18.04 (apt-cache policy openssl), however, it seems that on 1.1.0g is available.
From the documentation it does imply the only supported version is 16.04 (although I had no problems with 17.04, and 17.10 only needed a little tweaking). In the end I created a 16.04 container (using LXD/LXC) and then installed SQL Server on that. Then, afterwards, I pushed my databases files from the host machine to the container and reattached the databases.
Although you could create a 17.04 container, I'd recommend 16.04, as that's a LTS distribution. 17.04 ended support in January, 17.10's support ends in August (iirc), and 14.04 doesn't support SQL Server as far as I know.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
May 6, 2018 at 11:36 pm
Thom A - Sunday, May 6, 2018 10:13 AMI had no luck either I'm afraid Eirikur. It seems that, at the moment, SQL Server 2017 on Linux doesn't support OpenSSL 1.1.0g (which is odd, as to me that's version <=1.1.0 still, unless anything after the original is no good). I had a look at the versions available on 18.04 (apt-cache policy openssl), however, it seems that on 1.1.0g is available.From the documentation it does imply the only supported version is 16.04 (although I had no problems with 17.04, and 17.10 only needed a little tweaking). In the end I created a 16.04 container (using LXD/LXC) and then installed SQL Server on that. Then, afterwards, I pushed my databases files from the host machine to the container and reattached the databases.
Although you could create a 17.04 container, I'd recommend 16.04, as that's a LTS distribution. 17.04 ended support in January, 17.10's support ends in August (iirc), and 14.04 doesn't support SQL Server as far as I know.
Thanks Tom,
I'll go with the 16.04 container for now.
😎
May 8, 2018 at 10:21 am
16.04 here
May 8, 2018 at 3:42 pm
I just noticed that the comments at the bottom of the documentation for SQL Server on Linux is awash with this error at the moment on Ubuntu 18.04: https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-ubuntu?view=sql-server-linux-2017#next-steps. Seems that Microsoft are working on the fix, however, no ETA at this time.
This does, honestly, surprise me; considering how big they want to push the Linux releases. You expect a software vendor as big as Microsoft to have tested on future releases and worked on fixes ahead of time; or at least have a prepared ETA. The Alpha was released for 18.04 in Jan, and the Beta in March. I'd of thought that some "techie" in Microsoft would have tested against those and seen them problem quite early on; perhaps not.
I'll admit, it does make them look a little bad that they weren't ready for the next LTS version of Ubuntu. Non-LTS versions, fine (there's no point putting a large amount of effort into an OS version that's only supported by the vendor for 9 months), but you expect at least something in readiness for the full releases. It's almost like Oracle not having a working version of their RDBMS ready for Windows 10 when it came out.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
May 8, 2018 at 4:34 pm
I agree. I'd expect 18.04 support now, or at least soon.
May 9, 2018 at 8:31 am
Thom A - Tuesday, May 8, 2018 3:42 PMI just noticed that the comments at the bottom of the documentation for SQL Server on Linux is awash with this error at the moment on Ubuntu 18.04: https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-ubuntu?view=sql-server-linux-2017#next-steps. Seems that Microsoft are working on the fix, however, no ETA at this time.This does, honestly, surprise me; considering how big they want to push the Linux releases. You expect a software vendor as big as Microsoft to have tested on future releases and worked on fixes ahead of time; or at least have a prepared ETA. The Alpha was released for 18.04 in Jan, and the Beta in March. I'd of thought that some "techie" in Microsoft would have tested against those and seen them problem quite early on; perhaps not.
I'll admit, it does make them look a little bad that they weren't ready for the next LTS version of Ubuntu. Non-LTS versions, fine (there's no point putting a large amount of effort into an OS version that's only supported by the vendor for 9 months), but you expect at least something in readiness for the full releases. It's almost like Oracle not having a working version of their RDBMS ready for Windows 10 when it came out.
Hi Tom,
I'm doing something wrong, the LXD installation of the SQL Server is failing, can you share the configs please?
😎
May 9, 2018 at 8:55 am
Eirikur Eiriksson - Wednesday, May 9, 2018 8:31 AMHi Tom,
I'm doing something wrong, the LXD installation of the SQL Server is failing, can you share the configs please?
😎
Sure, you'll have to wait till I get home though I'm afraid; ever since I updated to 18.04 I've not been able to SSH from the office for some reason.
Are you getting any particular error messages as well?
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
May 9, 2018 at 10:59 am
Eirikur Eiriksson - Wednesday, May 9, 2018 8:31 AMHi Tom,
I'm doing something wrong, the LXD installation of the SQL Server is failing, can you share the configs please?
😎
Hi Eirikur. Not sure what details you'll need, so here's both the details of my default profile, which has been edited from the default, and the config settings. The changes to the profile were so that the container uses my router as the dns, rather than the host (I recall having to change my network adapters settings to set that up as well).thom@ihy:~$ lxc profile show default
config:
limits.memory: 2048MB
description: Default LXD profile
devices:
eth0:
name: eth0
nictype: bridged
parent: br0
type: nic
root:
path: /
pool: default
type: disk
name: default
used_by:
- /1.0/containers/qebui
thom@ihy:~$ lxc config show qebui
architecture: x86_64
config:
image.architecture: amd64
image.description: ubuntu 16.04 LTS amd64 (release) (20180427)
image.label: release
image.os: ubuntu
image.release: xenial
image.serial: "20180427"
image.version: "16.04"
volatile.base_image: 353b1a2c367ec983fd9d1532171618cd967e96d77a06f6b6e024c39ec010e8d7
volatile.eth0.hwaddr: 00:16:3e:78:5b:f0
volatile.idmap.base: "0"
volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
volatile.last_state.power: RUNNING
devices: {}
ephemeral: false
profiles:
- default
stateful: false
description: ""
The specific command I used to create the container was:lxc launch ubuntu:16.04 qebui
From there I followed the instructions in the document on how to install SQL Server on Linux: https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-ubuntu?view=sql-server-linux-2017
Feel free to give me a shout if you get stuck. Just let me know the errors you have. 🙂
Cheers!
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
May 11, 2018 at 3:52 am
Thanks for the help Tom.
Figured out the problem, the mssql-server didn't like the encrypted ZFS storage, changed it to dir and it works like a charm.
😎
May 11, 2018 at 9:56 am
That's interesting. Is encrypted storage the default?
May 11, 2018 at 10:16 am
Steve Jones - SSC Editor - Friday, May 11, 2018 9:56 AMThat's interesting. Is encrypted storage the default?
The default Filesystem on Ubuntu, at least prior to 18.04 was ext4 (I'm not aware it's changed). I haven't worked much with containers, apart from to get SQL Server working, or have multiple instances on a single instance (as multiple instances on the same server isn't supported (yet?)), but i would guess that the FS of the container is (by default) the same as the hosts. I'm therefore guessing Eirikur's FS is ZFS?
Does seem, according to the documentation, that the only supported file systems are XFS and ext4.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
May 11, 2018 at 11:28 am
If ZFS is installed, one has both native compression and encryption at hand, both coming from Solaris's brilliant file system. Handling sensitive data, using such a file system is a no-braner
😎
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply