Closed chrism closed 2 years ago
Thanks for this report. What architecture are you using?
Hi @toots you're welcome–sorry but I'm out of my depth with hardware questions.
It's a basic Digital Ocean shared CPU droplet but I couldn't really find anything more precise from their help page
If there are any specific details you need and you could aid me by explaining how I could find them out then I'm happy to do whatever I can.
We build our images for multiple architectures, amd54, arm 64 and 32 bits. We have had issues in the past with the arm 32bit image (the build process is a little more tricky). When do run the docker image savonet/liquidsoap:v2.1.2
, docker pulls the image corresponding to your actual architecture.
I have tested our arm 32 and 64 bit image as well as the amd64 images and they appear to work properly. I would suggest to look at your docker configuration to see if something might off, starting with security access/configuration.
Closing this for now, please feel free to re-open or report again if you see something coming from us.
Good luck!
Hi @chrism,
Could you post some information about your DO instance?
The docker info
output will be good for the beginning.
For me, this issue sounds like MariaDB/mariadb-docker#434.
For the first time, I used docker-ce=20.10.21
, and there was no problem there, but then I downgraded to docker-ce=20.10.7
.
I can reproduce this issue with the old docker version.
I think that the minimum required version is docker-ce=20.10.10
. Setting seccomp
to unconfined
will be fine too.
liquidsoap:
image: "savonet/liquidsoap:v2.1.2"
restart: always
command: ["/script.liq"]
ports:
- 7001:7001
environment:
ICECAST_SOURCE_PASSWORD: hackme
depends_on:
- icecast
security_opt:
- seccomp:unconfined
volumes:
- music:/music:ro
- ./script.liq:/script.liq:ro
Hi @vitoyucepi – sorry it took me a while to get back to you.
I just did a docker info
on my instance and here is the output... I think you are right it seems like it is 20.10.7
Client:
Context: default
Debug Mode: false
Plugins:
app: Docker App (Docker Inc., v0.9.1-beta3)
buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
scan: Docker Scan (Docker Inc., v0.8.0)
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 2
Server Version: 20.10.7
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc io.containerd.runc.v2 io.containerd.runtime.v1.linux
Default Runtime: runc
Init Binary: docker-init
containerd version: d71fcd7d8303cbf684402823e425e9dd2e99285d
runc version: b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 5.4.0-77-generic
Operating System: Ubuntu 20.04.2 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 981.2MiB
Name: dream-radio-player
ID: ZQU2:Z6S7:7G6D:6EUZ:FFNF:BXOJ:XF4I:BG5G:W4QU:3MQF:SIBG:FH3F
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Let me know if you want me to check anything else.
Thanks!
Hi @chrism,
The next step is to find out how to update it.
apt-cache policy docker-ce
will print all versions of docker-ce in the system package manager cache.
I'm assuming your docker installed using apt.
Seems like it must have been @vitoyucepi because this is the output...
docker-ce:
Installed: 5:20.10.7~3-0~ubuntu-focal
Candidate: 5:20.10.21~3-0~ubuntu-focal
Version table:
5:20.10.21~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.20~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.19~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.18~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.17~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.16~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.15~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.14~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.13~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.12~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.11~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.10~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.9~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.8~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
*** 5:20.10.7~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
100 /var/lib/dpkg/status
5:20.10.6~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.5~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.4~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.3~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.2~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.1~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:20.10.0~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:19.03.15~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:19.03.14~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:19.03.13~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:19.03.12~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:19.03.11~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:19.03.10~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
5:19.03.9~3-0~ubuntu-focal 500
500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
I think you should consider doing an update.
I recommend apt-get update && apt-get dist-upgrade
to get newer versions of all packages.
If you'd like to update only docker, then apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin
will do the trick.
This command should print something like
The following packages will be upgraded:
docker-ce docker-ce-cli containerd.io docker-compose-plugin
Maybe even do a do-release-upgrade
to upgrade to ubuntu:22.04
.
@chrism, you should remember that these changes could potentially break something. I'm not aware of your system setup, but doing a full system backup beforehand would be a great idea. Digital Ocean has a backup function to do that.
Thank you so much @vitoyucepi its too late for me to do this tonight but I will try tomorrow.
Really appreciate your advice.
TL;DR Updating the Digital Ocean droplet to Docker 20.10.21
resolved this issue and I am now running 2.1.2
in production.
I am not sure but maybe @toots it is worth documenting that while 2.1.0
supported Docker 20.10.7
, 2.1.2
no longer does (unless I have missed it and this is already documented)?
Once again thank you so much for your help @vitoyucepi, I followed your advice and updated using apt-get update && apt-get dist-upgrade
.
This successfully updated Docker to 20.10.21
and then just updating docker-compose.yml
to the latest liquidsoap version was enough to make it work.
Client: Context: default Debug Mode: false Plugins: app: Docker App (Docker Inc., v0.9.1-beta3) buildx: Docker Buildx (Docker Inc., v0.9.1-docker) scan: Docker Scan (Docker Inc., v0.21.0) Server: Containers: 2 Running: 0 Paused: 0 Stopped: 2 Images: 2 Server Version: 20.10.21 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc Default Runtime: runc Init Binary: docker-init containerd version: 770bd0108c32f3fb5c73ae1264f7e503fe7b2661 runc version: v1.1.4-0-g5fd4c4d init version: de40ad0 Security Options: apparmor seccomp Profile: default Kernel Version: 5.4.0-77-generic Operating System: Ubuntu 20.04.5 LTS OSType: linux Architecture: x86_64 CPUs: 1 Total Memory: 981.2MiB Name: dream-radio-player ID: ZQU2:Z6S7:7G6D:6EUZ:FFNF:BXOJ:XF4I:BG5G:W4QU:3MQF:SIBG:FH3F Docker Root Dir: /var/lib/docker Debug Mode: false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false
Hi @chrism,
This is a container engine problem. You can still use modern images on older docker by providing the command line option --security-opt seccomp=unconfined
or setting security_opt: [seccomp:unconfined]
in the docker-compose file.
For example, I've found an article about the problem https://medium.com/nttlabs/1cd439d9921.
P.S. Ubuntu 20.04 support will end in 2.5 years. Use Ubuntu 22.04 as a virtual machine template.
Thanks for posting this, I had the same issue. Upgrading docker solved it.
After updating the Docker image from v2.1.0 to v2.1.2 there is an error message on a fresh Digital Ocean droplet from their official Docker image (Docker
19.03.12
on Ubuntu20.04
).This is a minimal test case which works locally (on a mac), but fails when deployed.
Liquidsoap script which emits a sine to Icecast
And a
docker-compose.yml
file which uses the Liquidsoap and Icecast Docker imagesThe version above works both locally and on a droplet.
But after updating the Liquidsoap image from
savonet/liquidsoap:v2.1.0
tosavonet/liquidsoap:v2.1.2
there is this error message.20.04
2.1.2