Linux Package Manager Installation
- Add the ownCloud Repository
- Available Packages
- Avoid Automatic Upgrades
- Installing ownCloud Community Edition
- Installing ownCloud Enterprise Edition
- Additional Guides and Notes
You can use the packetmanager installation, but it is not recommended to do so. This is because somtimes dependencies are acting against each other like ownCloud version, minimum PHP version and Linux distribution restrictions. Anyone who runs a package manager installation should consider migrating to a manual installation to overcome this situation.
The recommended package to use is
It only installs ownCloud, and does not install Apache, a database, or any of the required PHP dependencies.
If you are installing ownCloud using one of the various Linux package managers, we strongly recommend that you avoid automatically updating the
owncloud-complete-files package, when running a system update or upgrade and when upgrading other packages.
That way, there are no surprise changes (whether positive or negative) to your ownCloud installation.
If you are using APT, use apt-mark hold to mark the
owncloud-complete-files package as held.
Here’s an example of how to do so:
apt-mark hold owncloud-complete-files
To see if owncloud-complete-files has already been held, use the
showhold command, as in the following example.
If it’s printed out to the console, then it’s being held.
apt-mark showhold owncloud-complete-files
owncloud-complete-files as held back, use the
unhold command, as in the example below.
apt-mark unhold owncloud-complete-files
If you are using Yum, there are two options that you can take to lock packages from being upgraded. You can:
Use the versionlock plugin for Yum.
versionlock plugin is not installed, install it by running:
yum install yum-plugin-versionlock
When it is installed, you can lock
yum versionlock add owncloud-complete-files
To confirm that it is locked, run:
yum versionlock list
yum versionlock delete owncloud-complete-files
If you are using Zypper, use the
apt-mark hold these add a package lock that prevents the package from being modified.
The example below shows how to use the command to lock
zypper addlock owncloud-complete-files
To see if the package has already been locked, use the
owncloud-complete-files is already locked, then you will see output similar to the below example.
# | Name | Type | Repository --+----------------+---------+----------- 1 | owncloud-complete-files | package | (any)
owncloud-complete-files, if it is already locked, use the
rl commands, as in the example below.
zypper removelock owncloud-complete-files
First, install your own LAMP stack, as doing so allows you to create your own custom LAMP stack without dependency conflicts with the ownCloud package. Then, update package manager’s configuration.
Configurations are available for the following Linux distributions:
Ubuntu 14.04 & 16.04
Debian 7 & 8
RHEL 6 & 7
CentOS 7.2 & 7.3
SLES 11SP4 & 12SP2
openSUSE Leap 42.2 & 42.3
|Repositories for Fedora, openSUSE Tumbleweed, and Ubuntu 15.04 have been dropped. If you use Fedora, use the tar archive with your own LAMP stack. openSUSE users can rely on LEAP packages for Tumbleweed.|
Once your package manager has been updated, follow the rest of the instructions on the download page to install ownCloud. Once ownCloud’s installed, run the Installation Wizard to complete your installation.
|See the system_requirements for the recommended ownCloud setup and supported platforms.|
|Do not move the folders provided by these packages after the installation, as this will break updates.|
Package versions are composed of a major, a minor, and a patch number, such as 9.0, 9.1, 10.0, 10.0.1, and 10.0.2. The second number represents a major release, and the third number represents a minor release.
If you want to follow either of the most recent major releases, then
version with either 9.0 or 10.0.
If you want to follow any of the four most recent patch releases, then
version with one of 10.0.1, 10.0.2, 10.0.3, or 10.0.4.
Following a minor release avoids you accidentally upgrading to the next
major release before you’re ready.
See the enterprise installation guide for instructions on installing ownCloud Enterprise edition.
Downgrading is not supported and risks corrupting your data! If you want to revert to an older ownCloud version, install it from scratch and then restore your data from backup. Before doing this, file a support ticket (if you have paid support) or ask for help in the ownCloud forums to see if your issue can be resolved without downgrading.
See installation_wizard for important steps, such as choosing the best database and setting correct directory permissions. See the SELinux guide for a suggested configuration for SELinux-enabled distributions such as Fedora and CentOS.
If your distribution is not listed, your Linux distribution may maintain its own ownCloud packages or you may prefer to install from source.
Please refer to MySQL / MariaDB with Binary Logging Enabled on how to correctly configure your environment if you have binary logging enabled.
If you’re running ownCloud in a sub-directory and want to use CalDAV or CardDAV clients, make sure you have configured the correct service discovery URLs.