Can't rebuild app with UTF8

Support
1

Hi everyone and thank you for great forum!

While trying to install akismet, running:
sudo ./launcher rebuild app
gives me such error:

Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
(<unknown>): found a tab character that violate intendation while scanning a plain scalar at line 91 column 13 -e LANG=en_US.UTF-8
YAML syntax error. Please check your containers/*.yml config files.

in my /containers/app.yml I have:

## Which Git revision should this container use? (default: tests-passed)
  #version: tests-passed

env:
  LANG: en_US.UTF-8
  # DISCOURSE_DEFAULT_LOCALE: en

Please help me to solve this issue

2

You have a tab in your yml file and that’s a problem.

The surest solution is to delete your yml file and run discourse-setup again. Or you can find the tab and replace it with spaces.

3

Thank you!
I find tab in config file, now I have another issue:

Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
cd /pups && git pull && /pups/bin/pups --stdin
/usr/bin/docker: Error response from daemon: error while creating mount source path '/var/discourse/shared/standalone': mkdir /var/discourse: read-only file system.
260dedf1e96919078211b6e422ba8297749d9418d13f27f69caa79b41926f98a
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

When I check free space it seems like that:

Filesystem      Size  Used Avail Use% Mounted on
udev            967M     0  967M   0% /dev
tmpfs           200M  1.2M  199M   1% /run
/dev/sda2        20G   12G  6.9G  64% /
tmpfs           997M     0  997M   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           997M     0  997M   0% /sys/fs/cgroup
/dev/loop4       89M   89M     0 100% /snap/core/6964
/dev/loop2       89M   89M     0 100% /snap/core/7169
/dev/loop0       98M   98M     0 100% /snap/docker/372
/dev/loop3       98M   98M     0 100% /snap/docker/381
/dev/loop1       98M   98M     0 100% /snap/docker/384
overlay          20G   12G  6.9G  64% /var/lib/docker/overlay2/7b5dec9e6d798e61769cdf211805b730ef2a667d2ce955d32a4438a09041c7d0/merged
shm             512M  8.0K  512M   1% /var/lib/docker/containers/7a906ebdc5d850c808edebc2625f161099b93c43f6f539f0376e013af8558b34/mounts/shm
tmpfs           200M     0  200M   0% /run/user/1000

What can it be? I use Ubuntu 18.04

4

There’s something wrong with your docker installation, how was docker installed?

What’s the result of doing:

docker info

The last time I saw this error the user had installed docker both from get.docker and separately via apt.

Did you install it using snap? That isn’t supported.

1 Like
5

Here is docker info output:

Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 18.06.1-ce
Storage Driver: aufs
 Root Dir: /var/snap/docker/common/var-lib-docker/aufs
 Backing Filesystem: extfs
 Dirs: 5
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: N/A (expected: 69663f0bd4b60df09991c08812a60108003fa340)
init version: 949e6fa (expected: fec3683)
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.15.0-52-generic
Operating System: Ubuntu Core 16
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.947GiB

ID: DPIA:C6E2:TFZY:6NRO:AOYZ:CHUV:ZPKC:KBYN:XXCA:IUMZ:D3FT:HRWS
Docker Root Dir: /var/snap/docker/common/var-lib-docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 22
 Goroutines: 44
 System Time: 2019-06-26T12:05:39.577235979Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

I used this tutorial to install, using GIT:

6

We don’t support that installation method here, the only supported install is the official install method.

Your docker info confirms that docker was installed using snap. Your options are to either ask DigitalOcean for support as you’ve followed their method, or use the official install method linked above.

1 Like
7

Oh, sure I will reinstall it, but please do you have official method for reinstalling? I am going to use CentOS and want to migrate container itself to new host.

8

The official install suggests ubuntu, I’m afraid you’re going to have to figure out how installation on CentOS will differ by yourself.

The scope of community support is limited, but if you have a budget you could also post over on the marketplace to have a consultant take a look.

9

Nevermind, if it is not Ubuntu issue but Snap, I will reinstall it. Thank you for your answer.

10

As I tryed several ways to make official install - it was no success.

  1. If I use official install and trying to restore backup using Web interface or CLI, I allways have FAILED state.

Then I think that it is good idea to remove docker and reinstall it. So I purge everything related docker by command:

sudo apt-get purge -y docker-engine docker docker.io docker-ce  
sudo apt-get autoremove -y --purge docker-engine docker docker.io docker-ce

After I trying

wget -qO- https://get.docker.com/ | sh

Everything is fine and

docker info

Shows no trace of snap. But as I trying to launch

./launcher rebuild app

I receive same error regarding read-only filesystem and

docker info

shows snap traces in path.

How to re-snap it?

11

That will not remove a docker installed with snap.

Run snap list | grep docker to find the snap package name, and the sudo snap remove ... to uninstall it.

4 Likes
12

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