You're executing Apache HTTPd in the foreground, so it's doing exactly what you're asking it to do. What you want to do is daemonize Apache, so script execution can continue.
How do to this depends on the way you (or your distribution) has set up Apache, but generally the following will do:
instead of apachectl -D FOREGROUND.
Do take note ...
By default Docker uses the bridge network driver (see the docs for more info). If you are running in this mode each container is, by default, added to the default bridge network.
Assuming that the above sums up your configuration (all defaults) then there is no need to map any host ports because the containers can communicate using the bridge network.
No answers, so I'm going to commnet my walkaround, it is not desired answer, but it's ok.
I finally setup a nginx working as reverse proxy listening to all interfaces. That was valid for me because it is http traffic.
I am also using dperson/samba with a exFAT mount, and was having similar issues with a Windows 10 client giving this error whenever I tried to rename/move/delete (but creating files worked)
Error 0x80070032: The request is not supported.
as you said, the fix was to remove fruit and streams_xattr from vfs objects line in /etc/samba/smb.conf
vfs objects = ...
Your image name is wrong. There's no equivalent for:
on Docker Hub. When you pull alpine:3.13.4, it is actually pulling docker.io/library/alpine:3.13.4. So your mirror needs to have the following image:
And the design of registry mirroring is to always go to the upstream source when ...
In my case the error read_passphrase: can't open /dev/tty: No such device or address was caused by ssh prompting for permission to add a new host.
As per this answer add to your ssh config
In case your ssh client supports it use accept-new instead of no for security.
The size of the final image ;-)
The first stage installs required binaries and libs to compile something and the next stage just copies the compiled stuff to an "empty" image.
You dont need to ship the whole build environment to run the software...
Valid steps in a Dockerfile include FROM, COPY, RUN, CMD, ENTRYPOINT, etc. The reference on the syntax is available at https://docs.docker.com/engine/reference/builder/
For your file I'd also recommend looking at the best practices, which would steer you towards:
RUN apt-get update \
&& apt-get install -y \
&& rm -...
Some more options:
add the --init switch to the container run command. This way, sleep is not PID 1, and init does the right thing on TERM.
add the --stop-signal=KILL to the container run command. Using KILL as a somewhat normal operation is generally discouraged however.
We had a very similar symptom running a docker-in-docker build in our CI pipeline, which runs in GKE. We suddenly started getting intermittent failures building Docker images when apt-get attempted to download packages from deb.debian.org (but also other hosts we tested manually, e.g. github.com). The problem was fixed in a similar way to that detailed by @...
I think it would be easier if you used the net use command within the container AFTER it has already started. I started the container with a gMSA and CredentialSpec, but I don't know if it is a requirement.
Within the container I executed net use D: \\ipaddress\c$ and it prompted me for my credentials:
The command was successful, now I executed net use ...
In this docker image php compilation a package is missing.
get inside the image and unpack the php tar
copy the config of phpinfo and append '--with-mysqli=mysqlnd'
install missing packages (various) xxx-dev libs including apache dev libs,
libxml-dev, sqlite3-dev, libssl-dev, zlib1g-dev,
libcurl4-openssl-dev, libonig-dev, libreadline-dev, libsodium-dev,