#Can't install on Ubuntu Server LTS, Other docker containers running, not using docker-compose

1 messages · Page 1 of 1 (latest)

rustic vaporBOT
#

:wave: Hey @tame blade,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich immich.

References

#

Checklist

I have...

  1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: read applicable release notes.
  3. :blue_square: reviewed the FAQs for known issues.
  4. :blue_square: reviewed Github for known issues.
  5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: uploaded the relevant information (see below).
  7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

  • Your docker-compose.yml and .env files.
  • Logs from all the containers and their status (see above).
  • All the troubleshooting steps you've tried so far.
  • Any recent changes you've made to Immich or your system.
  • Details about your system (both software/OS and hardware).
  • Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
  • The version of the Immich server, mobile app, and other relevant pieces.
  • Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

tawdry vessel
#

How did you install docker?

tame blade
#
computer@homeserver:/media/disk4$ docker ps -a
permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.47/containers/json?all=1": dial unix /var/run/docker.sock: connect: permission denied

pretty sure just the apt maybe I selected it in the server install, I'm about to google why I can't even get statuses now for my other two containers. Odd because I can still access my Kiwix server

#

now im scared to reboot the server lmao

#
computer@homeserver:/media/disk4$ docker info
Client:
 Version:    27.2.0
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.16.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.20.3
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
ERROR: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.47/info": dial unix /var/run/docker.sock: connect: permission denied
errors pretty printing info
full walrus
#

You should be using sudo

tame blade
#

Even if I use sudo same thing

#

even tried running as root sudo -u root docker compose up -d

full walrus
#

I feel like you have a very limited Linux knowledge .. given that you tried to chroot (?) to .env?

#

Where are you getting these commands from lol

#

Should be just sudo docker compose up -d

#

Idk what /media/disk4 is but the perms on that may be broken as well

tame blade
#

Right I understand that but I get the ermission denied error so I tried running it as root. It's the drive I was using to SMB photos now I was going to upgrade it to immich

#
open /media/disk4/.env: permission denied```
full walrus
#

Please try this: sudo cat /media/disk4/.env

tame blade
#

it's the example env

#
computer@homeserver:/media/disk4$ sudo cat /media/disk4/.env
# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables

# The location where your uploaded files are stored
UPLOAD_LOCATION=./library
# The location where your database files are stored
DB_DATA_LOCATION=./postgres

# To set a timezone, uncomment the next line and change Etc/UTC to a TZ identifier from this list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List
# TZ=Etc/UTC

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release

# Connection secret for postgres. You should change it to a random password
# Please use only the characters `A-Za-z0-9`, without special characters or spaces
DB_PASSWORD=postgres

# The values below this line do not need to be changed
###################################################################################
DB_USERNAME=postgres
DB_DATABASE_NAME=immich```
full walrus
#

Ok. I’m guessing you installed a non root docker or some weird setup

#

Please start over with this guide: https://docs.docker.com/engine/install/ubuntu/

Docker Documentation

Jumpstart your client-side server applications with Docker Engine on Ubuntu. This guide details prerequisites and multiple methods to install Docker Engine on Ubuntu.

tame blade
#

weird idk cause i just tried sudoing the container statuses and that worked as expected

#

will that fuck up my kiwix server if I reinstall docker?

#

its fine if it goes down just curous

full walrus
#

If you bring it down first then back up with the new docker should be fine

tame blade
#

okay got it, yea I don't use docker much and usually it just kinda works so idk what happened here

#

thanks I'll let ya know if i can't figure it out, usually pretty good at troubleshooting but I just wasn't even getting logs from docker compose logs

tawdry vessel
tame blade
#

no certainly not lmao

#

new to self hosting learning as I go using what I have available lmao

#

It's working now idk what was going on, I guess I chose docker as an additional package when installing ubunutu server.

#

although that doesn't really make sense still tbh