Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Discuss
  3. Ubuntu 22.04 LTS (Jammy Jellyfish) Beta

Ubuntu 22.04 LTS (Jammy Jellyfish) Beta

Scheduled Pinned Locked Moved Discuss
36 Posts 9 Posters 2.4k Views 9 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • nebulonN nebulon

    @RoboMod given that there is plenty of LTS time left on 20.04 I don't think we are in a rush to support it very soon. For a start I guess it makes to just wait a bit anyways for upstream to iron out any first hit issues.

    This also is related to binary releases of other components like docker, nginx, ... which we download explicitly from their repos instead of the Ubuntu ones.

    Then further the VPS provider often provider their own slightly changed Ubuntu variants, so also here I think it makes sense to wait a bit for them to settle.

    Of course, if there is a security issue or such, which requires us to act faster, then the situation changes.

    R Offline
    R Offline
    RoboMod
    wrote on last edited by
    #13

    @nebulon Thanks for the explanation! So, moving to 20.04 LTS first and upgrading later sounds reasonable.

    1 Reply Last reply
    0
    • girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #14

      Since this got released today, I tried to install Cloudron. Mostly everything works but nginx packages are not there yet - http://nginx.org/packages/ubuntu/pool/nginx/n/nginx/ . So, we have to wait till they provide the packages for ubuntu 22.04 (I tried older packages but they don't work because ubuntu 22 seems to use libssl3 instead of libssl1.1).

      robiR 1 Reply Last reply
      2
      • girishG girish

        Since this got released today, I tried to install Cloudron. Mostly everything works but nginx packages are not there yet - http://nginx.org/packages/ubuntu/pool/nginx/n/nginx/ . So, we have to wait till they provide the packages for ubuntu 22.04 (I tried older packages but they don't work because ubuntu 22 seems to use libssl3 instead of libssl1.1).

        robiR Offline
        robiR Offline
        robi
        wrote on last edited by
        #15

        @girish DB issue was resolved?

        Conscious tech

        girishG 1 Reply Last reply
        0
        • robiR robi

          @girish DB issue was resolved?

          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #16

          @robi yes, just had to select the right package in ubuntu 22.04 . Just https://git.cloudron.io/cloudron/box/-/commit/f5a2e8545b5e7e5c1d17a18790fccff0a5ea7669 was needed.

          robiR 1 Reply Last reply
          3
          • girishG girish

            @robi yes, just had to select the right package in ubuntu 22.04 . Just https://git.cloudron.io/cloudron/box/-/commit/f5a2e8545b5e7e5c1d17a18790fccff0a5ea7669 was needed.

            robiR Offline
            robiR Offline
            robi
            wrote on last edited by
            #17

            @girish sweet, thanks for the link.. it's clearer how all the changes in the front end script are also reflected in the backend init script.

            I'll try the new installer again,

            Thanks!

            Conscious tech

            1 Reply Last reply
            0
            • robiR robi

              https://lists.ubuntu.com/archives/ubuntu-announce/2022-March/000278.html

              https://releases.ubuntu.com/22.04/

              https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668

              LTS for 5 years

              Toolchain Upgrades 🛠
              Probably mention 🐍 Python 3.10 and 💎 ruby 3.0 and 🐪 perl and PHP.

              Security Improvements 🔒
              nftables is now the default backend for the firewall.

              ssh-rsa is now disabled by default in OpenSSH 31. See bug 1961833 19 to learn how to selectively re-enable it if necessary. If you are upgrading a system remotely over SSH, you should check that you are not relying on this to ensure that you will retain access after the upgrade.

              scp offers a -s command line option 6 to use sftp mode rather than scp mode 10 when handling remote filenames. This new, safer, behaviour will eventually become the default.

              Ubuntu Server
              Ubuntu HA/Clustering
              Corosync
              It was updated to version 3.16 which includes some new features:

              • Support for changing crypto configuration during runtime. This includes turning cryptography on or off, changing crypto_cipher and crypto_hash and also changing of crypto key.
              • Default token timeout was changed from 1 seconds to 3 seconds.
                / Run corosync -v to get the list of supported crypto and compression models which can be used in corosync.conf
              • Cgroup v2 support.

              ...

              Containers runtime
              containerd
              It was updated to version 1.5.9. Some interesting changes are:

              • Update pull to handle of non-https urls in descriptors
              • Install apparmor parser for arm64 and update seccomp to 2.5.1
              • Add support for clone3 syscall to fix issue with certain images when seccomp is enabled
              • Add image config labels in CRI container creation
                For the complete list of changes please refer to the upstream release page 2.

              runc
              It was updated to version 1.1.0. There are many improvements and bug fixes which can be found in the upstream release page. Some deprecations and removals which might impact the upgrade are presented below:

              Deprecation

              • runc run/start now warns if a new container cgroup is non-empty or frozen; this warning will become an error in runc 1.2
                Removals

              • cgroup.GetHugePageSizes has been removed entirely, and been replaced with cgroup.HugePageSizes which is more efficient

              • intelrdt.GetIntelRdtPath has been removed. Users who were using this function to get the intelrdt root should use the new intelrdt.Root instead.

              Ruby 3.0

              PHP now defaults to version 8.1.2

              OpenLDAP 2.5.x

              PostgreSQL 14

              MySQL 8.0

              And much more.. Discuss! Test!

              enJoy!

              L Offline
              L Offline
              LoudLemur
              wrote on last edited by
              #18

              @robi
              If you are trying 22.04 Jammy Jellyfish in a Virtual Machine, there can be issues with Wayland during login. (Scroll to 4:00 here:
              https://odysee.com/@DistroTube:2/is-ubuntu-22.04-the-best-ubuntu-in-years:f
              Mouse over to the bottom right and activate the dropdown menu there.
              Wayland isn't famous for playing well with proprietary nvidia drivers.
              If you want a leaner experience and Lubuntu, then there is a LxQt 1.1 PPA here:
              https://launchpad.net/~severusseptimius/+archive/ubuntu/lxqt

              robiR 1 Reply Last reply
              0
              • nebulonN nebulon

                @RoboMod given that there is plenty of LTS time left on 20.04 I don't think we are in a rush to support it very soon. For a start I guess it makes to just wait a bit anyways for upstream to iron out any first hit issues.

                This also is related to binary releases of other components like docker, nginx, ... which we download explicitly from their repos instead of the Ubuntu ones.

                Then further the VPS provider often provider their own slightly changed Ubuntu variants, so also here I think it makes sense to wait a bit for them to settle.

                Of course, if there is a security issue or such, which requires us to act faster, then the situation changes.

                L Offline
                L Offline
                LoudLemur
                wrote on last edited by
                #19

                @nebulon KDE neon usually waits till the x.04.1 release before proceeding with a major update. There is usually a load of people looking at a new LTS release, and tons of useful feedback.

                1 Reply Last reply
                1
                • L LoudLemur

                  @robi
                  If you are trying 22.04 Jammy Jellyfish in a Virtual Machine, there can be issues with Wayland during login. (Scroll to 4:00 here:
                  https://odysee.com/@DistroTube:2/is-ubuntu-22.04-the-best-ubuntu-in-years:f
                  Mouse over to the bottom right and activate the dropdown menu there.
                  Wayland isn't famous for playing well with proprietary nvidia drivers.
                  If you want a leaner experience and Lubuntu, then there is a LxQt 1.1 PPA here:
                  https://launchpad.net/~severusseptimius/+archive/ubuntu/lxqt

                  robiR Offline
                  robiR Offline
                  robi
                  wrote on last edited by
                  #20

                  @LoudLemur Slow your roll. There is no Wayland in a server install.

                  Conscious tech

                  L 1 Reply Last reply
                  2
                  • girishG Offline
                    girishG Offline
                    girish
                    Staff
                    wrote on last edited by girish
                    #21

                    I managed to mostly getting it working. Some interesting changes:

                    • cgroup v2 is enabled by default - https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html
                    • Private home directories by default - https://discourse.ubuntu.com/t/private-home-directories-for-ubuntu-21-04-onwards/
                    • nginx upstream has not offered jammy binaries yet, so we have reverted to using ubuntu packages for nginx. On ubuntu 18 alone, we continue to use upstream packages for TLS v1.3
                    • Python 3 default
                    1 Reply Last reply
                    3
                    • robiR robi

                      @LoudLemur Slow your roll. There is no Wayland in a server install.

                      L Offline
                      L Offline
                      LoudLemur
                      wrote on last edited by
                      #22

                      @robi Haha! Thank you, @robi!

                      1 Reply Last reply
                      1
                      • d19dotcaD Offline
                        d19dotcaD Offline
                        d19dotca
                        wrote on last edited by d19dotca
                        #23

                        I noticed that Cloudron still has the install instructions for 20.04... does this mean we don't yet recommend using 22.04 at the moment? Or are the docs just a bit outdated? @staff

                        I noticed the Cloudron marketplace app in Vultr uses 22.04 now, so just was wondering about those inconsistencies in the docs and marketplace apps.

                        --
                        Dustin Dauncey
                        www.d19.ca

                        subvenS 1 Reply Last reply
                        2
                        • d19dotcaD d19dotca

                          I noticed that Cloudron still has the install instructions for 20.04... does this mean we don't yet recommend using 22.04 at the moment? Or are the docs just a bit outdated? @staff

                          I noticed the Cloudron marketplace app in Vultr uses 22.04 now, so just was wondering about those inconsistencies in the docs and marketplace apps.

                          subvenS Offline
                          subvenS Offline
                          subven
                          wrote on last edited by
                          #24

                          @d19dotca installation on a clean 22.04 failed for me lately so while it is working with some small adjustments, it is not stable out of the box right now. At least from what I saw is that you can upgrade from 20.04 to 22.04.

                          1 Reply Last reply
                          3
                          • girishG Offline
                            girishG Offline
                            girish
                            Staff
                            wrote on last edited by
                            #25

                            @d19dotca So, with Cloudron 7.3, we will make the default to be ubuntu 22. I am not aware of pending issues as such.

                            That said,

                            @d19dotca installation on a clean 22.04 failed for me lately so while it is working with some small adjustments, it is not stable out of the box right now. At least from what I saw is that you can upgrade from 20.04 to 22.04.

                            @subven do you know where it was failing? It should be in /var/log/cloudron-setup.log . If you tell me which VPS provider, I can test it out as well.

                            subvenS 1 Reply Last reply
                            1
                            • girishG girish

                              @d19dotca So, with Cloudron 7.3, we will make the default to be ubuntu 22. I am not aware of pending issues as such.

                              That said,

                              @d19dotca installation on a clean 22.04 failed for me lately so while it is working with some small adjustments, it is not stable out of the box right now. At least from what I saw is that you can upgrade from 20.04 to 22.04.

                              @subven do you know where it was failing? It should be in /var/log/cloudron-setup.log . If you tell me which VPS provider, I can test it out as well.

                              subvenS Offline
                              subvenS Offline
                              subven
                              wrote on last edited by
                              #26

                              @girish unbound related but I did not dig into it nor saved logs. Sadly I have option to test again.

                              1 Reply Last reply
                              0
                              • d19dotcaD Offline
                                d19dotcaD Offline
                                d19dotca
                                wrote on last edited by
                                #27

                                Just curious if there was an update to this... was there a genuine issue with the 22.04 install/operation with Cloudron @subven / @girish ? Considering upgrading to 22.04 later this year just to be more up-to-date (I realize there isn't really a real-world issue to require upgrading yet but it's just my OCD, lol), so was just curious about the status / reliability on 22.04.

                                --
                                Dustin Dauncey
                                www.d19.ca

                                subvenS 1 Reply Last reply
                                1
                                • d19dotcaD d19dotca

                                  Just curious if there was an update to this... was there a genuine issue with the 22.04 install/operation with Cloudron @subven / @girish ? Considering upgrading to 22.04 later this year just to be more up-to-date (I realize there isn't really a real-world issue to require upgrading yet but it's just my OCD, lol), so was just curious about the status / reliability on 22.04.

                                  subvenS Offline
                                  subvenS Offline
                                  subven
                                  wrote on last edited by
                                  #28

                                  @d19dotca there should be no issue to upgrade to 22.04 LTS. Take a look at the documentation. Just had trouble to install Cloudron on some VPS that came with 22.04 vendor images. Never tested it again since 7.3 but since you don't read a lot of topics about it in the forums, it should work fine.

                                  1 Reply Last reply
                                  2
                                  • andreasduerenA Offline
                                    andreasduerenA Offline
                                    andreasdueren
                                    wrote on last edited by
                                    #29

                                    How long is re-creating the containers supposed to take more or less? Its been about three hours now and I'm not sure if things are supposed to go this way…Screenshot 2022-11-24 at 14.17.46.png

                                    andreasduerenA 1 Reply Last reply
                                    0
                                    • andreasduerenA andreasdueren

                                      How long is re-creating the containers supposed to take more or less? Its been about three hours now and I'm not sure if things are supposed to go this way…Screenshot 2022-11-24 at 14.17.46.png

                                      andreasduerenA Offline
                                      andreasduerenA Offline
                                      andreasdueren
                                      wrote on last edited by
                                      #30

                                      @andreasdueren Both, box and collectd are running. But the Dashboard is not available. To reboot or not to reboot is the question.Screenshot 2022-11-24 at 14.59.45.png

                                      girishG 1 Reply Last reply
                                      0
                                      • andreasduerenA andreasdueren

                                        @andreasdueren Both, box and collectd are running. But the Dashboard is not available. To reboot or not to reboot is the question.Screenshot 2022-11-24 at 14.59.45.png

                                        girishG Offline
                                        girishG Offline
                                        girish
                                        Staff
                                        wrote on last edited by
                                        #31

                                        @andreasdueren If you check the box logs, there is probably some error when upgrading the platform . See /home/yellowtent/platformdata/logs/box.log

                                        andreasduerenA 1 Reply Last reply
                                        0
                                        • girishG girish

                                          @andreasdueren If you check the box logs, there is probably some error when upgrading the platform . See /home/yellowtent/platformdata/logs/box.log

                                          andreasduerenA Offline
                                          andreasduerenA Offline
                                          andreasdueren
                                          wrote on last edited by
                                          #32

                                          @girish said in Ubuntu 22.04 LTS (Jammy Jellyfish) Beta:

                                          /home/yellowtent/platformdata/logs/box.log

                                          Indeed:

                                          2022-11-24T21:06:30.744Z box:services startServices: 48.0.0 -> 49.2.0. starting all services
                                          2022-11-24T21:06:30.746Z box:mail restartMail: restarting mail container with mailFqdn:mail.[domain name] mailDomain:[domain name]
                                          2022-11-24T21:06:30.787Z box:shell stopMail exec: docker stop mail || true
                                          2022-11-24T21:06:30.841Z box:shell stopMail (stdout): null
                                          2022-11-24T21:06:30.841Z box:shell stopMail (stderr): Error response from daemon: No such container: mail
                                          
                                          2022-11-24T21:06:30.842Z box:shell removeMail exec: docker rm -f mail || true
                                          2022-11-24T21:06:30.903Z box:shell removeMail (stdout): null
                                          2022-11-24T21:06:30.903Z box:shell removeMail (stderr): Error: No such container: mail
                                          2022-11-24T21:06:30.904Z box:mail createMailConfig: generating mail config with mail.[domain name]
                                          2022-11-24T21:06:30.917Z box:shell startMail exec: docker run --restart=always -d --name="mail"                 --net cloudron                 --net-alias mail                 --log-driver syslog                 --log-opt syslog-address=udp://127.0.0.1>
                                          2022-11-24T21:06:31.241Z box:shell startMail (stdout): 2b2204feb19c61d40ebe444686af469e5f5c877b1655ebf570dcaa6cc55e0715
                                          
                                          2022-11-24T21:06:31.241Z box:shell startMail (stderr): null
                                          2022-11-24T21:06:31.256Z box:shell stopTurn exec: docker stop turn || true
                                          2022-11-24T21:06:31.323Z box:shell stopTurn (stdout): null
                                          2022-11-24T21:06:31.324Z box:shell stopTurn (stderr): Error response from daemon: No such container: turn
                                          
                                          2022-11-24T21:06:31.324Z box:shell removeTurn exec: docker rm -f turn || true
                                          2022-11-24T21:06:31.387Z box:shell removeTurn (stdout): null
                                          2022-11-24T21:06:31.387Z box:shell removeTurn (stderr): Error: No such container: turn
                                          
                                          
                                          2022-11-24T21:06:31.387Z box:shell startTurn exec: docker run --restart=always -d --name="turn"                 --hostname turn                 --net host                 --log-driver syslog                 --log-opt syslog-address=udp://127.0.0.1:2514>
                                          2022-11-24T21:06:31.711Z box:shell startTurn (stdout): 7cc6bc9cd1c5ede10dedcf45a0eef9b586813952471fda3416c146456b9d63ea
                                          
                                          2022-11-24T21:06:31.711Z box:shell startTurn (stderr): null
                                          2022-11-24T21:06:31.714Z box:shell stopMysql exec: docker stop mysql || true
                                          2022-11-24T21:06:31.778Z box:shell stopMysql (stdout): null
                                          2022-11-24T21:06:31.778Z box:shell stopMysql (stderr): Error response from daemon: No such container: mysql
                                          
                                          2022-11-24T21:06:31.778Z box:shell removeMysql exec: docker rm -f mysql || true
                                          2022-11-24T21:06:31.844Z box:shell removeMysql (stdout): null
                                          2022-11-24T21:06:31.844Z box:shell removeMysql (stderr): Error: No such container: mysql
                                          
                                          2022-11-24T21:06:31.845Z box:shell startMysql exec: docker run --restart=always -d --name="mysql"                 --hostname mysql                 --net cloudron                 --net-alias mysql                 --log-driver syslog                 --lo>
                                          2022-11-24T21:06:32.531Z box:shell startMysql (stdout): adbd1aaf01de166f9fddfd9b95594a74239d6de01021a7f21cac84847e35bc30
                                          
                                          2022-11-24T21:06:32.531Z box:shell startMysql (stderr): null
                                          2022-11-24T21:06:32.532Z box:services Waiting for mysql
                                          2022-11-24T21:06:32.554Z box:services Attempt 1 failed. Will retry: Network error waiting for mysql: connect ECONNREFUSED 172.18.0.3:3000
                                          2022-11-24T21:06:47.861Z box:shell stopPostgresql exec: docker stop postgresql || true
                                          2022-11-24T21:06:47.922Z box:shell stopPostgresql (stdout): null
                                          2022-11-24T21:06:47.923Z box:shell stopPostgresql (stderr): Error response from daemon: No such container: postgresql
                                          
                                          2022-11-24T21:06:47.923Z box:shell removePostgresql exec: docker rm -f postgresql || true
                                          2022-11-24T21:06:47.974Z box:shell removePostgresql (stdout): null
                                          2022-11-24T21:06:47.974Z box:shell removePostgresql (stderr): Error: No such container: postgresql
                                          
                                          2022-11-24T21:06:47.975Z box:shell startPostgresql exec: docker run --restart=always -d --name="postgresql"                 --hostname postgresql                 --net cloudron                 --net-alias postgresql                 --log-driver syslog >
                                          2022-11-24T21:06:48.634Z box:shell startPostgresql (stdout): 83c3240c0a3c8cb42473f6b7910ac85bf5ca9f069bcab0468e288a9d6f296380
                                          
                                          2022-11-24T21:06:48.635Z box:shell startPostgresql (stderr): null
                                          2022-11-24T21:06:48.635Z box:services Waiting for postgresql
                                          2022-11-24T21:06:48.641Z box:services Attempt 1 failed. Will retry: Network error waiting for postgresql: connect ECONNREFUSED 172.18.0.4:3000
                                          2022-11-24T21:07:03.970Z box:shell stopMongodb exec: docker stop mongodb || true
                                          2022-11-24T21:07:04.023Z box:shell stopMongodb (stdout): null
                                          2022-11-24T21:07:04.023Z box:shell stopMongodb (stderr): Error response from daemon: No such container: mongodb
                                          
                                          2022-11-24T21:07:04.024Z box:shell removeMongodb exec: docker rm -f mongodb || true
                                          2022-11-24T21:07:04.082Z box:shell removeMongodb (stdout): null
                                          2022-11-24T21:07:04.082Z box:shell removeMongodb (stderr): Error: No such container: mongodb
                                          
                                          2022-11-24T21:07:04.083Z box:shell startMongodb exec: docker run --restart=always -d --name="mongodb"                 --hostname mongodb                 --net cloudron                 --net-alias mongodb                 --log-driver syslog             >
                                          2022-11-24T21:07:04.792Z box:shell startMongodb (stdout): fc403f98af1f812acce8d0d3c33a35f7c416e5b813baca29366e7def22b72731
                                          
                                          2022-11-24T21:07:04.792Z box:shell startMongodb (stderr): null
                                          2022-11-24T21:07:04.792Z box:services Waiting for mongodb
                                          2022-11-24T21:07:04.796Z box:services Attempt 1 failed. Will retry: Network error waiting for mongodb: connect ECONNREFUSED 172.18.0.5:3000
                                          2022-11-24T21:07:08.765Z box:box Received SIGTERM. Shutting down.
                                          2022-11-24T21:07:08.766Z box:tasks stopAllTasks: stopping all tasks
                                          2022-11-24T21:07:08.766Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
                                          2022-11-24T21:07:08.801Z box:shell stopTask (stdout): sudo: unable to resolve host my: No address associated with hostname
                                          2022-11-24T21:07:12.855Z box:server ==========================================
                                          2022-11-24T21:07:12.856Z box:server            Cloudron 7.3.2
                                          2022-11-24T21:07:12.856Z box:server ==========================================
                                          2022-11-24T21:07:12.912Z box:settings initCache: pre-load settings
                                          2022-11-24T21:07:12.926Z box:tasks stopAllTasks: stopping all tasks
                                          2022-11-24T21:07:12.926Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
                                          2022-11-24T21:07:12.940Z box:shell stopTask (stdout): sudo: unable to resolve host my: No address associated with hostname
                                          
                                          Cloudron is up and running. Logs are at /home/yellowtent/platformdata/logs/box.log
                                          2022-11-24T21:07:12.968Z box:reverseproxy writeDashboardConfig: writing admin config for [domain name]
                                          2022-11-24T21:07:12.994Z box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
                                          2022-11-24T21:07:13.002Z box:shell reload (stdout): sudo: unable to resolve host my: No address associated with hostname
                                          
                                          2022-11-24T21:07:13.011Z box:shell reload (stdout): nginx: [emerg] open() "/etc/nginx/nginx.conf" failed (2: No such file or directory)
                                          
                                          2022-11-24T21:07:13.013Z box:shell reload code: 1, signal: null
                                          2022-11-24T21:07:13.014Z box:cloudron Startup task at index 1 failed: Error reloading nginx: reload exited with code 1 signal null BoxError: Error reloading nginx: reload exited with code 1 signal null
                                          	at reload (/home/yellowtent/box/src/reverseproxy.js:183:22)
                                          	at processTicksAndRejections (node:internal/process/task_queues:96:5)
                                          	at async writeDashboardNginxConfig (/home/yellowtent/box/src/reverseproxy.js:429:5)
                                          	at async Object.writeDashboardConfig (/home/yellowtent/box/src/reverseproxy.js:440:5)
                                          	at async Array.<anonymous> (/home/yellowtent/box/src/cloudron.js:117:9)
                                          2022-11-24T21:07:13.017Z box:cloudron onActivated: running post activation tasks
                                          2022-11-24T21:07:13.017Z box:platform initializing addon infrastructure
                                          2022-11-24T21:07:13.018Z box:platform Updating infrastructure from 48.0.0 to 49.2.0
                                          2022-11-24T21:07:13.019Z box:locker Acquired : platform_start
                                          2022-11-24T21:07:13.019Z box:platform removeAllContainers: removing all containers for infra upgrade
                                          2022-11-24T21:07:13.019Z box:shell removeAllContainers exec: docker ps -qa --filter 'label=isCloudronManaged' | xargs --no-run-if-empty docker stop
                                          2022-11-24T21:07:23.423Z box:shell removeAllContainers (stdout): fc403f98af1f
                                          83c3240c0a3c
                                          adbd1aaf01de
                                          7cc6bc9cd1c5
                                          2b2204feb19c
                                          
                                          2022-11-24T21:07:23.423Z box:shell removeAllContainers (stderr): null
                                          2022-11-24T21:07:23.423Z box:shell removeAllContainers exec: docker ps -qa --filter 'label=isCloudronManaged' | xargs --no-run-if-empty docker rm -f
                                          2022-11-24T21:07:23.544Z box:shell removeAllContainers (stdout): fc403f98af1f
                                          83c3240c0a3c
                                          adbd1aaf01de
                                          7cc6bc9cd1c5
                                          2b2204feb19c
                                          
                                          2022-11-24T21:07:23.544Z box:shell removeAllContainers (stderr): null
                                          2022-11-24T21:07:23.544Z box:platform createDockerNetwork: recreating docker network
                                          2022-11-24T21:07:23.544Z box:shell createDockerNetwork exec: docker network rm cloudron || true
                                          2022-11-24T21:07:23.760Z box:shell createDockerNetwork (stdout): cloudron
                                          
                                          2022-11-24T21:07:23.760Z box:shell createDockerNetwork (stderr): null
                                          2022-11-24T21:07:23.760Z box:shell createDockerNetwork exec: docker network create --subnet=172.18.0.0/16 --ip-range=172.18.0.0/20 --gateway 172.18.0.1 --ipv6 --subnet=fd00:c107:d509::/64 cloudron
                                          2022-11-24T21:07:23.943Z box:shell createDockerNetwork (stdout): 52e23202af728b794c1a44bf4440f893e601dc51a56fb840e3eb0d46b9757a7c
                                          
                                          2022-11-24T21:07:23.943Z box:shell createDockerNetwork (stderr): null
                                          2022-11-24T21:07:23.944Z box:platform markApps: reconfiguring installed apps
                                          2022-11-24T21:07:23.944Z box:reverseproxy removeAppConfigs: reomving nginx configs of apps
                                          2022-11-24T21:07:23.954Z box:services startServices: 48.0.0 -> 49.2.0. starting all services
                                          2022-11-24T21:07:23.956Z box:mail restartMail: restarting mail container with mailFqdn:mail.[domain name] mailDomain:[domain name]
                                          2022-11-24T21:07:24.002Z box:shell stopMail exec: docker stop mail || true
                                          2022-11-24T21:07:24.066Z box:shell stopMail (stdout): null
                                          2022-11-24T21:07:24.067Z box:shell stopMail (stderr): Error response from daemon: No such container: mail
                                          
                                          2022-11-24T21:07:24.067Z box:shell removeMail exec: docker rm -f mail || true
                                          2022-11-24T21:07:24.130Z box:shell removeMail (stdout): null
                                          2022-11-24T21:07:24.130Z box:shell removeMail (stderr): Error: No such container: mail
                                          
                                          2022-11-24T21:07:24.067Z box:shell removeMail exec: docker rm -f mail || true
                                          2022-11-24T21:07:24.130Z box:shell removeMail (stdout): null
                                          2022-11-24T21:07:24.130Z box:shell removeMail (stderr): Error: No such container: mail
                                          
                                          2022-11-24T21:07:24.131Z box:mail createMailConfig: generating mail config with mail.[domain name]
                                          2022-11-24T21:07:24.137Z box:shell startMail exec: docker run --restart=always -d --name="mail"                 --net cloudron                 --net-alias mail                 --log-driver syslog                 --log-opt syslog-address=udp://127.0.0.1>
                                          2022-11-24T21:07:24.977Z box:shell startMail (stdout): 24cc35c6baf48e4b310d48a30fbfad9bb3b1fa09188bafba8ef3eb36f74e599a
                                          
                                          2022-11-24T21:07:24.977Z box:shell startMail (stderr): null
                                          2022-11-24T21:07:24.992Z box:shell stopTurn exec: docker stop turn || true
                                          2022-11-24T21:07:25.044Z box:shell stopTurn (stdout): null
                                          2022-11-24T21:07:25.044Z box:shell stopTurn (stderr): Error response from daemon: No such container: turn
                                          
                                          2022-11-24T21:07:25.044Z box:shell removeTurn exec: docker rm -f turn || true
                                          2022-11-24T21:07:25.108Z box:shell removeTurn (stdout): null
                                          2022-11-24T21:07:25.108Z box:shell removeTurn (stderr): Error: No such container: turn
                                          
                                          2022-11-24T21:07:25.108Z box:shell startTurn exec: docker run --restart=always -d --name="turn"                 --hostname turn                 --net host                 --log-driver syslog                 --log-opt syslog-address=udp://127.0.0.1:2514>
                                          2022-11-24T21:07:25.331Z box:shell startTurn (stdout): 4d3c37483e529d0591f68613680e451183d313261e59a9ca04450a8469ec41a0
                                          
                                          2022-11-24T21:07:25.331Z box:shell startTurn (stderr): null
                                          2022-11-24T21:07:25.334Z box:shell stopMysql exec: docker stop mysql || true
                                          2022-11-24T21:07:25.385Z box:shell stopMysql (stdout): null
                                          2022-11-24T21:07:25.385Z box:shell stopMysql (stderr): Error response from daemon: No such container: mysql
                                          
                                          2022-11-24T21:07:25.386Z box:shell removeMysql exec: docker rm -f mysql || true
                                          2022-11-24T21:07:25.442Z box:shell removeMysql (stdout): null
                                          2022-11-24T21:07:25.442Z box:shell removeMysql (stderr): Error: No such container: mysql
                                          
                                          2022-11-24T21:07:25.442Z box:shell startMysql exec: docker run --restart=always -d --name="mysql"                 --hostname mysql                 --net cloudron                 --net-alias mysql                 --log-driver syslog                 --lo>
                                          2022-11-24T21:07:26.068Z box:shell startMysql (stdout): 6c935e6a3534fdbc2453c342f9fb1abf7e2a790e08201b86cf58a13232e88370
                                          
                                          2022-11-24T21:07:26.068Z box:shell startMysql (stderr): null
                                          2022-11-24T21:07:26.068Z box:services Waiting for mysql
                                          2022-11-24T21:07:26.088Z box:services Attempt 1 failed. Will retry: Network error waiting for mysql: connect ECONNREFUSED 172.18.0.3:3000
                                          2022-11-24T21:07:41.364Z box:shell stopPostgresql exec: docker stop postgresql || true
                                          2022-11-24T21:07:41.421Z box:shell stopPostgresql (stdout): null
                                          2022-11-24T21:07:41.421Z box:shell stopPostgresql (stderr): Error response from daemon: No such container: postgresql
                                          
                                          2022-11-24T21:07:41.421Z box:shell removePostgresql exec: docker rm -f postgresql || true
                                          2022-11-24T21:07:41.484Z box:shell removePostgresql (stdout): null
                                          2022-11-24T21:07:41.485Z box:shell removePostgresql (stderr): Error: No such container: postgresql
                                          
                                          2022-11-24T21:07:41.485Z box:shell startPostgresql exec: docker run --restart=always -d --name="postgresql"                 --hostname postgresql                 --net cloudron                 --net-alias postgresql                 --log-driver syslog >
                                          2022-11-24T21:07:42.110Z box:shell startPostgresql (stdout): 1d914aad11019b2c8a3fb00bdfd50d8631fa1c08d22502ae15b03d84958fef38
                                          
                                          2022-11-24T21:07:42.110Z box:shell startPostgresql (stderr): null
                                          2022-11-24T21:07:42.110Z box:services Waiting for postgresql
                                          2022-11-24T21:07:42.118Z box:services Attempt 1 failed. Will retry: Network error waiting for postgresql: connect ECONNREFUSED 172.18.0.4:3000
                                          
                                          
                                          andreasduerenA 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Bookmarks
                                          • Search