如何使用控制台安装更新

您好,Discourse 的各位。

我收到通知,我的 Discourse 站点有 34 个更新可供安装,但我不知道如何安装它们。有人知道要输入什么命令来安装它们吗?是否有不安装所有这些更新的理由?

以下是 Ubuntu 23.10 的更新列表:

cloud-init/mantic-updates 23.3.3-0ubuntu0~23.10.1 all [upgradable from: 23.3.1-0ubuntu2]

containerd.io/mantic 1.6.26-1 amd64 [upgradable from: 1.6.24-1]

distro-info-data/mantic-updates 0.58ubuntu0.1 all [upgradable from: 0.58]

initramfs-tools-bin/mantic-updates 0.142ubuntu15.1 amd64 [upgradable from: 0.142ubuntu15]

initramfs-tools-core/mantic-updates 0.142ubuntu15.1 all [upgradable from: 0.142ubuntu15]

initramfs-tools/mantic-updates 0.142ubuntu15.1 all [upgradable from: 0.142ubuntu15]

libnetplan0/mantic-updates 0.107-5ubuntu0.2 amd64 [upgradable from: 0.107-5]

libnss-systemd/mantic-updates 253.5-1ubuntu6.1 amd64 [upgradable from: 253.5-1ubuntu6]

libpam-systemd/mantic-updates 253.5-1ubuntu6.1 amd64 [upgradable from: 253.5-1ubuntu6]

libsgutils2-1.46-2/mantic-updates 1.46-3ubuntu2.1 amd64 [upgradable from: 1.46-3ubuntu2]

libsystemd-shared/mantic-updates 253.5-1ubuntu6.1 amd64 [upgradable from: 253.5-1ubuntu6]

libsystemd0/mantic-updates 253.5-1ubuntu6.1 amd64 [upgradable from: 253.5-1ubuntu6]

libudev1/mantic-updates 253.5-1ubuntu6.1 amd64 [upgradable from: 253.5-1ubuntu6]

netplan-generator/mantic-updates 0.107-5ubuntu0.2 amd64 [upgradable from: 0.107-5]

netplan.io/mantic-updates 0.107-5ubuntu0.2 amd64 [upgradable from: 0.107-5]

python3-distupgrade/mantic-updates 1:23.10.14 all [upgradable from: 1:23.10.10]

python3-netplan/mantic-updates 0.107-5ubuntu0.2 amd64 [upgradable from: 0.107-5]

sg3-utils-udev/mantic-updates 1.46-3ubuntu2.1 all [upgradable from: 1.46-3ubuntu2]

sg3-utils/mantic-updates 1.46-3ubuntu2.1 amd64 [upgradable from: 1.46-3ubuntu2]

snapd/mantic-updates 2.60.4+23.10.1 amd64 [upgradable from: 2.60.4+23.10]

systemd-dev/mantic-updates 253.5-1ubuntu6.1 all [upgradable from: 253.5-1ubuntu6]

systemd-hwe-hwdb/mantic-updates 253.5.2 all [upgradable from: 253.5.1]

systemd-resolved/mantic-updates 253.5-1ubuntu6.1 amd64 [upgradable from: 253.5-1ubuntu6]

systemd-sysv/mantic-updates 253.5-1ubuntu6.1 amd64 [upgradable from: 253.5-1ubuntu6]

systemd-timesyncd/mantic-updates 253.5-1ubuntu6.1 amd64 [upgradable from: 253.5-1ubuntu6]

systemd/mantic-updates 253.5-1ubuntu6.1 amd64 [upgradable from: 253.5-1ubuntu6]

tmux/mantic-updates 3.3a-4ubuntu1 amd64 [upgradable from: 3.3a-4]

ubuntu-advantage-tools/mantic-updates 30~23.10 amd64 [upgradable from: 29.4]

ubuntu-minimal/mantic-updates 1.524.1 amd64 [upgradable from: 1.524]

ubuntu-release-upgrader-core/mantic-updates 1:23.10.14 all [upgradable from: 1:23.10.10]

ubuntu-server/mantic-updates 1.524.1 amd64 [upgradable from: 1.524]

ubuntu-standard/mantic-updates 1.524.1 amd64 [upgradable from: 1.524]

udev/mantic-updates 253.5-1ubuntu6.1 amd64 [upgradable from: 253.5-1ubuntu6]

我尝试输入“install”,但不起作用。

我不是计算机专业人士。

**install --help:**

尝试“install --help”以获取更多信息。
root@community:~# install --help
Usage: install [OPTION]... [-T] SOURCE DEST
  or:  install [OPTION]... SOURCE... DIRECTORY
  or:  install [OPTION]... -t DIRECTORY SOURCE...
  or:  install [OPTION]... -d DIRECTORY...

This install program copies files (often just compiled) into destination
locations you choose.  If you want to download and install a ready-to-use
package on a GNU/Linux system, you should instead be using a package manager
like yum(1) or apt-get(1).

In the first three forms, copy SOURCE to DEST or multiple SOURCE(s) to
the existing DIRECTORY, while setting permission modes and owner/group.
In the 4th form, create all components of the given DIRECTORY(ies).

Mandatory arguments to long options are mandatory for short options too.
      --backup[=CONTROL]  make a backup of each existing destination file
  -b                  like --backup but does not accept an argument
  -c                  (ignored)
  -C, --compare       compare content of source and destination files, and
                        if no change to content, ownership, and permissions,
                        do not modify the destination at all
  -d, --directory     treat all arguments as directory names; create all
                        components of the specified directories
  -D                  create all leading components of DEST except the last,
                        or all components of --target-directory,
                        then copy SOURCE to DEST
  -g, --group=GROUP   set group ownership, instead of process' current group
  -m, --mode=MODE     set permission mode (as in chmod), instead of rwxr-xr-x
  -o, --owner=OWNER   set ownership (super-user only)
  -p, --preserve-timestamps   apply access/modification times of SOURCE files
                        to corresponding destination files
  -s, --strip         strip symbol tables
      --strip-program=PROGRAM  program used to strip binaries
  -S, --suffix=SUFFIX  override the usual backup suffix
  -t, --target-directory=DIRECTORY  copy all SOURCE arguments into DIRECTORY
  -T, --no-target-directory  treat DEST as a normal file
  -v, --verbose       print the name of each directory as it is created
      --preserve-context  preserve SELinux security context
  -Z                      set SELinux security context of destination
                            file and each created directory to default type
      --context[=CTX]     like -Z, or if CTX is specified then set the
                            SELinux or SMACK security context to CTX
      --help        display this help and exit
      --version     output version information and exit

The backup suffix is '~', unless set with --suffix or SIMPLE_BACKUP_SUFFIX.
The version control method may be selected via the --backup option or through
the VERSION_CONTROL environment variable.  Here are the values:

  none, off       never make backups (even if --backup is given)
  numbered, t     make numbered backups
  existing, nil   numbered if numbered backups exist, simple otherwise
  simple, never   always make simple backups

GNU coreutils online help: <https://www.gnu.org/software/coreutils/>
Report any translation bugs to <https://translationproject.org/team/>
Full documentation <https://www.gnu.org/software/coreutils/install>
or available locally via: info '(coreutils) install invocation'

您好,

对于服务器更新,您可以在 Ubuntu 上使用 apt upgrade

顺便说一下,这与 Discourse 没有直接关系。在标准安装中,Discourse 将位于 Docker 容器内。

谢谢,这似乎可以开始安装过程。
这可能意味着标准安装未正确完成,您如何判断 Discourse 是否在 Docker 中?

这也很令人困惑,Docker 在其中列出但未选中。

5. 安装 Docker 的先决条件(基于 Debian/Ubuntu 的发行版示例)

sudo apt install docker.io
sudo apt install git

算了。按 Tab 键并高亮显示 <ok>,然后按 Enter 键。

这是正确的方法,谢谢。

现在似乎有一个奇怪的错误,当一个站点的安装被中断时,它说仍然有 34 个更新可以应用,但当我尝试运行安装时:

root@community:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

编辑:

重建应用程序现在看起来像有一个对接:

atus: Downloaded newer image for discourse/base:2.0.20231218-0429
docker.io/discourse/base:2.0.20231218-0429
Ensuring launcher is up to date
Launcher is up-to-date
Stopping old container
+ /usr/bin/docker stop -t 600 app

有很多警告,这是正常的还是表示有问题?

warning 分辨率字段“unset-value@2.0.1”与请求的版本“unset-value@^1.0.0”不兼容
warning 模式 [“wrap-ansi@^7.0.0”] 正在尝试解压到与模式 [“wrap-ansi-cjs@npm:wrap-ansi@^7.0.0”] 相同的目标“/home/discourse/.cache/yarn/v6/npm-wrap-ansi-cjs-7.0.0-67e145cff510a6a6984bdf1152911d69d2eb9e43-integrity/node_modules/wrap-ansi-cjs”。这可能导致非确定性行为,正在跳过。
warning “ > discourse-markdown-it@1.0.0”有未满足的对等依赖项“xss@*”。
warning “workspace-aggregator-387500e6-104d-417d-9e2e-53cf67ffdfce > discourse > @ember/legacy-built-in-components@0.5.0”有不正确的对等依赖项“ember-source@>= 4.8”。
warning “workspace-aggregator-387500e6-104d-417d-9e2e-53cf67ffdfce > discourse > @uppy/aws-s3@3.0.6”有不正确的对等依赖项“@uppy/core@^3.1.2”。
warning “workspace-aggregator-387500e6-104d-417d-9e2e-53cf67ffdfce > discourse > @uppy/aws-s3-multipart@3.1.3”有不正确的对等依赖项“@uppy/core@^3.1.2”。
warning “workspace-aggregator-387500e6-104d-417d-9e2e-53cf67ffdfce > discourse > @uppy/xhr-upload@3.1.1”有不正确的对等依赖项“@uppy/core@^3.1.2”。
warning “workspace-aggregator-387500e6-104d-417d-9e2e-53cf67ffdfce > discourse-plugins > ember-this-fallback@0.4.0”有未满足的对等依赖项“ember-source@^3.28.11 || ^4.0.0”。
warning “workspace-aggregator-387500e6-104d-417d-9e2e-53cf67ffdfce > discourse > @uppy/aws-s3 > @uppy/xhr-upload@3.3.0”有不正确的对等依赖项“@uppy/core@^3.2.1”。

警告是预期的,是的。您可以安全地忽略它们。 :+1:

1 个赞

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.