SOLVED App: docker-compose (portainer) - Help needed

SecCon

Contributor
Joined
Dec 16, 2017
Messages
175
I have tried the jailmaker script - it works. Not done anything with it yet - but the debian jail runs.
So from Jip-Hop's post and what you write above you are making a jail, installing an OS (Debian) and running the Docker from there. Correct me if I am wrong, but considering Scale is Debian, you kinda install Debian in Debian to run Docker because the first OS layer ( Scale / Debian ) is unable do it better?
Is it really only me who find that ... strange?
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
Its a seperate instance, on its own IP and isn't subject (that I am aware of) to the crappy routing that the native K3S has. The Jail has access to the full CPU & Memory of the host - which a docker VM doesn't

At the moment its a toy - it may turn into something more important
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
Just to confirm - it doesn't have the routing bug that exists in the IX implementation of K3S. I didn't think it would - but its nice to see traffic going where it should rather than all at the LAN side default gateway.
 

Mortorojo

Cadet
Joined
May 25, 2023
Messages
8
Please Help, When trying to lauch portainer in docker-compose it always gets stuck on:

2023-05-26T03:49:25.279407120Z time="2023-05-26T03:49:25.279331894Z" level=info msg="Daemon has completed initialization"
2023-05-26T03:49:25.596296733Z time="2023-05-26T03:49:25.596125079Z" level=info msg="API listen on [::]:2376"
2023-05-26T03:49:25.603176805Z time="2023-05-26T03:49:25.603028794Z" level=info msg="API listen on /var/run/docker.sock"
2023-05-26T03:49:34.995187482Z 2023/05/26 03:49:34 http: TLS handshake error from 172.16.0.1:39420: EOF
2023-05-26T03:49:34.995610598Z 2023/05/26 03:49:34 http: TLS handshake error from 172.16.0.1:39430: EOF

I've attached the logs. My compose file is same listed above in thread, /mnt has been mounted as Host Path, and K8s Host Path Validation is disabled.
 

Attachments

  • potainer_log.txt
    10.9 KB · Views: 142

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
If this is docker-compose/portainer in a scale-jail - is the file exactly the same as the one listed in this thread

If this is docker-compose in a Truechart K3S App - then please post your own thread
 

marksd

Cadet
Joined
Jul 8, 2023
Messages
1
Hi everyone. I'm extreamly new to all this. I found this page trying to find a way to get this to work. I noticed the link to the instructions to show how this works is not working any more. Is there any new documentation for this anywhere? BTW, I'm on a Truenas Scale server.
 

slacks425

Dabbler
Joined
Aug 6, 2023
Messages
13
I'm more or less in the same boat, I managed to install portainer, I guess, it's deployed but when I enter serverIP:8000 or 9443 the ports specified in the docker-compose file, nothing load (unable to connect).

Here is my docker-compose.yml file I give as inpuit when deploying the docker-compose (TrueCharts app):

Code:
Code:

version: '3'
services:
  portainer:
    image: cr.portainer.io/portainer/portainer-ce:latest
    container_name: portainer
    restart: always
    networks:
      - portainer
    ports:
      - "8000:8000"
      - "9443:9443"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /mnt/jet/appdata/portainer:/data

networks:
  portainer:
    external: false


Any help is welcome.
 
Top