Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
dmv.community is one of the many independent Mastodon servers you can use to participate in the fediverse.
A small regional Mastodon instance for those in the DC, Maryland, and Virginia areas. Local news, commentary, and conversation.

Administered by:

Server stats:

155
active users

dmv.community: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#dockercompose

1 post1 participant0 posts today
Public
blogger | retronerd.AT

Writefreely mit Docker Compose
Hallo.Heute wollen wir mit Docker die Opensource Software writefreely erstellen.Dazu solltest Du über eine Ubuntu VM (24.04) mit einer Dockerumgebung verfügen und SSH Zugang haben.

1. Installation von wget

apt install wget -y

2. Erstellen des notwendigen Docker-Netzwerks

docker network create -
blog.retronerd.at/writefreely-
#docker #fediverse #docker #dockercompose #fediverse #opensource #tutorial #ubuntu #writefreely

blog.retronerd.at · Writefreely mit Docker Compose - blog.retronerd.at
More from SchiWaGoA
Public
Lanie Molinar Carmelo

I'm curious to hear what others are #SelfHosting! Here's my current setup:

Hardware & OS

Infrastructure & Networking

Security & Monitoring

Authentication & Identity Management

  • Authelia (Docker): Just set this up for two-factor authentication and single sign-on. Seems to be working well so far!
  • LLDAP (Docker): Lightweight LDAP server for managing authentication. Also seems to be working pretty well!
    #AuthenticationTools #IdentityManagement

Productivity & Personal Tools

Notifications & Development Workflow

  • Notifications via: #Ntfy (Docker) and Zoho's ZeptoMail (#Zoho)
  • Development Environment: Mostly using VSCode connected to my server via Remote-SSH extension. #VSCodeRemote

Accessibility Focus ♿️🖥️

Accessibility heavily influences my choices—I use a screen reader full-time (#ScreenReader), so I prioritize services usable without sight (#InclusiveDesign, #DigitalAccessibility). Always open to discussing accessibility experiences or recommendations!

I've also experimented with:

  • Ollama (#Ollama): Not enough RAM on my Pi.
  • Habit trackers like Beaver Habit Tracker (#HabitTracking): Accessibility issues made it unusable for me.

I don't really have a media collection, so no Plex or Jellyfin here (#MediaServer)—but I'm always open to suggestions! I've gotten a bit addicted to exploring new self-hosted services! 😄

What's your setup like? Any cool services you'd recommend I try?

#SelfHosted #LinuxSelfHost #OpenSource #TechCommunity #FOSS #TechDIY

@selfhost @selfhosted @selfhosting

Public
algernon ludd

As the next step in my quest to make it easier to poison AI crawlers, I present you: OCIocaine: a project where #DockerCompose meets #Caddy and #Iocaine, to poison AI crawlers for all your sites, automatically.

The idea here is to provide a docker compose file that starts up Caddy and Iocaine, configured so that Caddy will reverse proxy for any and all services on the same docker network, as long as they have a few labels that tell it to do so. In addition, a Caddyfile snippet will be available for all of these, which takes care of routing bad visitors to Iocaine.

And if that's not enough, the whole thing comes preconfigured with a wordlist (a list of English words), and traning data (the complete works of Shakespeare), and a list of known AI crawlers (courtesy of ai.robots.txt).

All you have to do is copy the sample configuration, create a network, start it up, and deploy labeled containers into the same network, and OCIocaine takes care of the rest.

MadHouse Git RepositoriesociocaineDocker Compose meets Caddy and Iocaine to poison AI for all your sites, automatically.
Public
Nicolas Delsaux

Comment passer correctement des secrets à docker-compose.
Ca n'est généralement pas un problème dans les environments K8s, où docker-compose n'est utilisé que sur le poste des développeurs, mais ça peut aider dans d'autres environnements ... phase.dev/blog/docker-compose- #dockercompose #secret #configuration #programming #devops

phaseManaging Secrets in Docker Compose — A Developer's Guide | Phase BlogA practical guide to securely managing secrets in Docker Compose for production deployments
Replied in thread
Public
Jack Linke 🦄

In the process of trying to identify the cause of the problem, I also learned just what a pain it is to get strace working in #DockerCompose.

- Just add the SYS_PTRACE capability, right?
- Or maybe also set the seccomp:unconfined security_option?
- Or run as privileged?
- And try every combination of these and half a dozen other config options?

Nope 🤡 Still have not gotten strace to attach, but I'll keep working at this one, because it seems a useful tool to have available.

Fun times 😆

Replied in thread
Public
slamp

I summarize: I have #zombie processes created by #wget command when doing an https request in the #healthcheck section of #DockerCompose

Zombie processes occur when child processes have completed execution, and their exit status needs to be read by the parent process.

A process in a #container is still a process on the host, so it takes up a PID on the host. Whatever you run in a container is PID 1 which means it has to install a signal handler to get that signal.

8/n

Replied in thread
Public *
slamp

I checked that I set the parameter to not check the certificate as i'm using 127.0.0.1 instead of the FQDN and #letsencrypt don't provide #certificate for IP addresses

I exec inside the #docker container to run manually the `wget --no-check-certificate`

It's working correctly

When I remove the healthcheck section in #DockerCompose there is no more #zombie process

Root cause found: It's the wget used by the healthcheck that create the zombies !

7/n

healthcheck: test: ["CMD-SHELL", "wget --no-check-certificate -q -O - https://127.0.0.1:9090/api/v1/status/runtimeinfo | grep st atus > /dev/null"] interval: 60s timeout: 5s retries: 5 start_period: 20s
Result of the command wget --no-check-certificate -q -O - https://127.0.0.1:9090/api/v1/status/runtimeinfo | grep status
Replied in thread
Public *
slamp

Time for investigation.

I checked one of the parent and found [ssl_client] <defunct>

I checked a second parent and found [wget] <defunct>

This reminded me that the last change I made was to enable #https using #letsencrypt certificate for most services

#wget is used in the healthcheck section inside #dockerCompose but it doesn't explain the zombie, or may be ?

6/n

screenshot showing the process with <defunct>
screenshot showing the process with <defunct>
ExploreLive feeds
About